Triple

T1033931
Position Surface form Disambiguated ID Type / Status
Subject Nassau Veterans Memorial Coliseum E22315 entity
Predicate distanceFromManhattan P2383 FINISHED
Object approximately 19 miles east 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: approximately 19 miles east | Statement: [Nassau Veterans Memorial Coliseum, distanceFromManhattan, approximately 19 miles east]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distanceFromManhattan
Context triple: [Nassau Veterans Memorial Coliseum, distanceFromManhattan, approximately 19 miles east]
  • A. distanceCharacteristic
    Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
  • B. flightDistance
    Indicates the measured distance covered by a flight between its origin and destination.
  • C. distanceToNewYorkCity chosen
    Indicates the spatial distance between a given entity’s location and New York City.
  • D. distanceFromDowntown
    Indicates the physical distance between a given location and the central downtown area.
  • E. distanceFromSanFrancisco
    Indicates the measured distance between a given entity’s location and the city of San Francisco.
  • 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_69a493d848848190aed4011b34b2e8d3 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b8d669448190955507e2e4975b9f completed March 1, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69a4b728ad3481909cf1430349cb9bba completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:41 p.m.