Triple

T9580691
Position Surface form Disambiguated ID Type / Status
Subject 2009 Fort Totten crash E231160 entity
Predicate lineSegment P17813 FINISHED
Object between Takoma and Fort Totten stations 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: between Takoma and Fort Totten stations | Statement: [2009 Fort Totten crash, lineSegment, between Takoma and Fort Totten stations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lineSegment
Context triple: [2009 Fort Totten crash, lineSegment, between Takoma and Fort Totten stations]
  • A. lineElement chosen
    Indicates a relationship where something functions as, or is identified as, an element or segment of a line within a larger linear structure or representation.
  • B. lineSymbol
    Indicates that one entity is used as a line-style or line-representation symbol for another entity.
  • C. lineExtendedTo
    Indicates that one line is formed by extending another line beyond its original endpoint.
  • D. lineCorridor
    Indicates that one entity is a corridor represented or approximated by a line, typically modeling a narrow passageway or path between areas.
  • E. lineType
    Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
  • F. None of above.

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_69ca848091c48190bc313d6620d09555 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd99cbe79081909947b4d1389eb015 completed April 1, 2026, 10:18 p.m.
PD Predicate disambiguation batch_69ccd59fd7408190b36831902e3f37f7 completed April 1, 2026, 8:21 a.m.
Created at: March 30, 2026, 8:05 p.m.