Triple
T19371605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwin Denison Morgan |
E484551
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Morgan |
—
|
NE NERFINISHED |
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: Morgan | Statement: [Edwin Denison Morgan, familyName, Morgan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Morgan Context triple: [Edwin Denison Morgan, familyName, Morgan]
-
A.
Morgan
Morgan is a Chicago 'L' rapid transit station on the Near West Side serving the city's Pink and Green Lines.
-
B.
Morgan
Morgan is a common Welsh surname with deep cultural and historical roots in Wales and among people of Welsh descent.
-
C.
Morgan
chosen
Morgan is a prominent American banking and finance family name most famously associated with financier J. P. Morgan and the powerful House of Morgan banking dynasty.
-
D.
Morgan
Morgan is a common English surname borne by numerous notable individuals across fields such as science, finance, and entertainment.
-
E.
Morgan
Morgan is the second-generation core design used in AMD's Duron processors, featuring improvements in performance and efficiency over the original Spitfire core.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619b09ef08190a8b420316c0b8eb3 |
completed | April 20, 2026, 12:18 p.m. |
Created at: April 10, 2026, 1:35 p.m.