Triple

T22006861
Position Surface form Disambiguated ID Type / Status
Subject James Dunlop E543468 entity
Predicate familyName P18 FINISHED
Object Dunlop 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: Dunlop | Statement: [James Dunlop, familyName, Dunlop]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dunlop
Context triple: [James Dunlop, familyName, Dunlop]
  • A. Dunlop
    Dunlop is a well-known tire manufacturer that produces high-performance motorcycle and automotive tires used in both professional racing and everyday driving.
  • B. Dunlop
    Dunlop is a residential suburb in the Belconnen district of Canberra, in the Australian Capital Territory.
  • C. Dunlop
    Dunlop is the middle name of A. D. Lindsay, a British academic and philosopher.
  • D. Dunlop chosen
    Dunlop is a surname of Scottish and Irish origin borne by numerous notable individuals across fields such as motorsport, music, and manufacturing.
  • E. Goodyear
    Goodyear is a rapidly growing suburban city in the Phoenix metropolitan area of Arizona, known for its master-planned communities, spring training baseball facilities, and proximity to desert recreation.
  • 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_69e11e2db934819095556760c7d85e4d completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127a18c1081909d15aa7ed4b725e3 completed April 28, 2026, 9:33 p.m.
Created at: April 16, 2026, 8:21 p.m.