Triple

T3816710
Position Surface form Disambiguated ID Type / Status
Subject Kingston–Rhinecliff Bridge E84272 entity
Predicate replacedPlanned P36091 FINISHED
Object originally proposed Kingston–Rhinecliff ferry replacement 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: originally proposed Kingston–Rhinecliff ferry replacement | Statement: [Kingston–Rhinecliff Bridge, replacedPlanned, originally proposed Kingston–Rhinecliff ferry replacement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: replacedPlanned
Context triple: [Kingston–Rhinecliff Bridge, replacedPlanned, originally proposed Kingston–Rhinecliff ferry replacement]
  • A. plannedReplacement chosen
    Indicates that one entity is intended or scheduled to be replaced by another entity in the future.
  • B. replacedDuring
    Indicates that one entity took the place of another entity during a specified time period or interval.
  • C. placedBy
    Indicates that one entity was positioned, set, or put in a location or context by another entity.
  • D. planned
    Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
  • E. plannedUnder
    Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of 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_69aed931f5908190be2c07af66d4df25 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aef1515c688190a38332aedeed8a76 completed March 9, 2026, 4:12 p.m.
PD Predicate disambiguation batch_69aee7482d708190a3ec74745b102a4c completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:17 p.m.