Triple
T9110563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monty Woolley |
E218589
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Edgar |
E39303
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Edgar | Statement: [Monty Woolley, givenName, Edgar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Edgar Context triple: [Monty Woolley, givenName, Edgar]
-
A.
Edgar
chosen
Edgar is the first name of Edgar Allan Poe, the influential 19th-century American writer known for his macabre poetry and pioneering detective fiction.
-
B.
Edgar
Edgar was an English royal figure of the late 10th century, notable as the son of King Æthelred the Unready.
-
C.
Edwin
Edwin is a masculine given name of Old English origin meaning "rich friend" or "prosperous friend."
-
D.
Edgar Wesley
Edgar Wesley was an American Negro league first baseman known for his powerful hitting during the 1920s, particularly with the Detroit Stars.
-
E.
Roderick
Roderick is a masculine given name of Germanic origin, historically associated with leaders and nobility and used in various forms across European languages.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca847102881908f9d86ce9883fb1a |
completed | April 1, 2026, 5:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d030467b188190a6d99bf2fc65207d |
completed | April 3, 2026, 9:25 p.m. |
Created at: March 30, 2026, 7:16 p.m.