Triple

T27352720
Position Surface form Disambiguated ID Type / Status
Subject R. H. Saunders Generating Station E684405 entity
Predicate neighboringStateAcrossRiver P382 FINISHED
Object New York NE NERFINISHED

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: New York | Statement: [R. H. Saunders Generating Station, neighboringStateAcrossRiver, New York]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: neighboringStateAcrossRiver
Context triple: [R. H. Saunders Generating Station, neighboringStateAcrossRiver, New York]
  • A. nearbyCountryAcrossRiver
    Indicates that one country is located close to another country with a river lying between them as a separating feature.
  • B. locatedAcrossRiverFrom chosen
    Indicates that one entity is situated on the opposite side of a river relative to another entity.
  • C. borderedByCountryAcrossRiver
    Indicates that one country shares a border with another country, with the boundary specifically formed or separated by a river.
  • D. borderingOpposingState
    Indicates that one state shares a border with another state that is politically, militarily, or ideologically opposed to it.
  • E. bordersAcrossRiver
    Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
  • 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_69ef1480a76481908684256ddd5bfda3 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f66c5c13808190887180099745673b completed May 2, 2026, 9:27 p.m.
PD Predicate disambiguation batch_69f66abddc448190a488852f8abdeb2c completed May 2, 2026, 9:21 p.m.
Created at: April 27, 2026, 11:49 a.m.