Triple

T6926727
Position Surface form Disambiguated ID Type / Status
Subject Aberdare Line E160328 entity
Predicate terminus P388 FINISHED
Object Aberdare E97367 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: Aberdare | Statement: [Aberdare Line, terminus, Aberdare]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aberdare
Context triple: [Aberdare Line, terminus, Aberdare]
  • A. Aberdare chosen
    Aberdare is a town in the Cynon Valley of Rhondda Cynon Taf, Wales, historically known for its coal mining and ironworks industries.
  • B. Torresdale
    Torresdale is a residential neighborhood in the far northeastern section of Philadelphia, Pennsylvania, known for its proximity to the Delaware River and suburban character.
  • C. Kearsley
    Kearsley is a town in Greater Manchester, England, historically part of Lancashire and known for its industrial heritage.
  • D. Duffield
    Duffield is a village and civil parish in Derbyshire, England, situated north of Derby on the River Derwent.
  • E. Kineton
    Kineton is a village in Warwickshire, England, known for its proximity to the historic Edgehill battlefield of the English Civil War.
  • 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_69c6884d350081908d8a970e4d40ad78 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6da1aa9c48190b63a04be2ed9e266 completed March 27, 2026, 7:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7514359148190b87b39efc8e714a8 completed March 28, 2026, 3:55 a.m.
Created at: March 27, 2026, 2:27 p.m.