Triple
T11460385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin Morgan |
E271641
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Morgan |
E459318
|
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: Morgan | Statement: [Colin Morgan, familyName, Morgan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Morgan Context triple: [Colin 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 the party that successfully defended the constitutionality of a key provision of the Voting Rights Act in the landmark U.S. Supreme Court case Katzenbach v. Morgan.
-
C.
Morgan
chosen
Morgan is a common English surname borne by numerous notable individuals across fields such as science, finance, and entertainment.
-
D.
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.
-
E.
Morgan
Morgan is a residential neighborhood within the borough of Sayreville in Middlesex County, New Jersey.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f384f08190b1150ed1389dd31a |
completed | April 9, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5e91f1bb881909a9c36d837e4059b |
completed | April 20, 2026, 8:51 a.m. |
Created at: April 8, 2026, 9:35 p.m.