Triple

T37620402
Position Surface form Disambiguated ID Type / Status
Subject Danny Ford E936050 entity
Predicate overallRecordAtArkansas P189079 FINISHED
Object 20–21–1 LITERAL 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: 20–21–1 | Statement: [Danny Ford, overallRecordAtArkansas, 20–21–1]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: overallRecordAtArkansas
Context triple: [Danny Ford, overallRecordAtArkansas, 20–21–1]
  • A. overallRecordAtOklahoma
    Indicates the overall performance record (such as wins and losses) that an entity has achieved while associated with Oklahoma.
  • B. overallRecordAtMissouri
    Indicates the overall performance or win-loss record that an entity has achieved while competing at Missouri.
  • C. hasCountyNumberInArkansas
    Indicates that an entity is assigned a specific official county number within the state of Arkansas.
  • D. metropolitanAreaPopulationRankInArkansas
    Indicates the rank order of a metropolitan area's population size compared to other metropolitan areas within the state of Arkansas.
  • E. MississippiStateAchievement
    Indicates a relationship where an entity attains or is recognized for a notable accomplishment specifically associated with the state of Mississippi.
  • F. None of above. chosen

Provenance (4 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_69f76ed16b748190ad6add183b1be688 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbb084760c8190a1554985d3c3cb7a completed May 6, 2026, 9:20 p.m.
PD Predicate disambiguation batch_69fbadf3cb548190ba3b7514f76b790a completed May 6, 2026, 9:09 p.m.
PDg Predicate description generation batch_69fbb083ab708190a18b045311106f27 completed May 6, 2026, 9:20 p.m.
Created at: May 3, 2026, 4:18 p.m.