Triple

T3907501
Position Surface form Disambiguated ID Type / Status
Subject Lindsey Horan E87237 entity
Predicate familyName P18 FINISHED
Object Horan E87237 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: Horan | Statement: [Lindsey Horan, familyName, Horan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horan
Context triple: [Lindsey Horan, familyName, Horan]
  • A. Horan chosen
    Horan is a surname most prominently associated with American soccer player Lindsey Horan.
  • B. Forristal
    Forristal is a surname of Irish origin borne by various individuals, including those in the arts and public life.
  • C. Rostrevor
    Rostrevor is a picturesque village in County Down, Northern Ireland, known for its scenic setting between the Mourne Mountains and Carlingford Lough.
  • D. Curraheen
    Curraheen is a suburban area on the outskirts of Cork city in Ireland, known for its residential communities and proximity to local amenities and transport links.
  • E. Lorne
    Lorne is a masculine given name most notably associated with Canadian-American television producer and "Saturday Night Live" creator Lorne Michaels.
  • 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_69aed9424514819086e9c58adde6652d completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeed1290e48190aaf2d8b2a7be707a completed March 9, 2026, 3:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69b51caf41c881909c5156480b46e794 completed March 14, 2026, 8:30 a.m.
Created at: March 9, 2026, 3:22 p.m.