Triple

T4527001
Position Surface form Disambiguated ID Type / Status
Subject Colt Stadium E106202 entity
Predicate distanceFromSuccessor P21270 FINISHED
Object adjacent to Astrodome site 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: adjacent to Astrodome site | Statement: [Colt Stadium, distanceFromSuccessor, adjacent to Astrodome site]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distanceFromSuccessor
Context triple: [Colt Stadium, distanceFromSuccessor, adjacent to Astrodome site]
  • A. distanceFromPredecessor
    Indicates the measured distance separating an entity from the one that immediately precedes it in a sequence or ordering.
  • B. distanceToSuccessorStadium chosen
    Indicates the measured distance between a stadium and the stadium that directly succeeds it in a defined sequence or timeline.
  • C. distanceFromTerminus
    Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
  • D. successorDeterminedBy
    Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
  • E. distancedFrom
    Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
  • 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_69bd43f3d6e08190a91824f833d51bbe completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd57760f4481908f69ce82be63d7f8 completed March 20, 2026, 2:19 p.m.
PD Predicate disambiguation batch_69bd521cf77c819083852de3094d1377 completed March 20, 2026, 1:56 p.m.
Created at: March 20, 2026, 1:03 p.m.