Triple
T15894008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Flanagan (British political adviser) |
E385403
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Flanagan |
E71593
|
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: Flanagan | Statement: [Mark Flanagan (British political adviser), familyName, Flanagan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Flanagan Context triple: [Mark Flanagan (British political adviser), familyName, Flanagan]
-
A.
Flanagan
chosen
Flanagan is a surname of Irish origin borne by numerous notable individuals across fields such as politics, sports, literature, and science.
-
B.
Flanigan
Flanigan is a surname variant of Flanagan, an Irish family name of Gaelic origin.
-
C.
O'Flanagan
O'Flanagan is an Irish surname, a variant of Flanagan, traditionally associated with Gaelic heritage and families originating in Ireland.
-
D.
Flaherty
Flaherty is an Irish surname of Gaelic origin, derived from the Ó Flaithbheartaigh family name.
-
E.
Flaherty
Flaherty is an unincorporated community located in Meade County, Kentucky, United States.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1563809748190a54156b946d3f061 |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb5a1b1548190a8579cebf9e71121 |
completed | May 9, 2026, 10:30 p.m. |
Created at: April 10, 2026, 4:51 a.m.