Triple

T6961171
Position Surface form Disambiguated ID Type / Status
Subject Bakken formation region E161370 entity
Predicate transportConstraint P33452 FINISHED
Object pipeline capacity 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: pipeline capacity | Statement: [Bakken formation region, transportConstraint, pipeline capacity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transportConstraint
Context triple: [Bakken formation region, transportConstraint, pipeline capacity]
  • A. transportRestriction chosen
    Indicates that there are limitations, prohibitions, or special conditions governing the use of a particular mode or means of transportation between entities.
  • B. trafficRestriction
    Indicates a limitation or prohibition on the movement or flow of traffic between entities, such as vehicles, routes, or areas.
  • C. transportAssumption
    Indicates an assumption that something can be transported or carried from one place or context to another.
  • D. transportModeAccess
    Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
  • E. hasLimitedRoadAccess
    Indicates that an entity can only be reached by a small number of roads, restricted routes, or otherwise constrained vehicular access.
  • 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_69c68852a9a0819097797e31d492e273 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6daeee4d48190b078beeebb0053f4 completed March 27, 2026, 7:30 p.m.
PD Predicate disambiguation batch_69c6d7c0b0a08190b262dfc94992994d completed March 27, 2026, 7:17 p.m.
Created at: March 27, 2026, 2:29 p.m.