Triple

T9764443
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 131 E236749 entity
Predicate followsTransportationCorridorType P56025 FINISHED
Object north–south route 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: north–south route | Statement: [Maine State Route 131, followsTransportationCorridorType, north–south route]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: followsTransportationCorridorType
Context triple: [Maine State Route 131, followsTransportationCorridorType, north–south route]
  • A. railCorridorType
    Indicates the specific classification or type of a rail corridor associated with the subject (e.g., mainline, branch line, high-speed, freight, etc.).
  • B. transportCorridor
    Indicates a route or pathway used to move people, goods, or resources between locations.
  • C. partOfTransportCorridorTo
    Indicates that one entity forms a component or segment of a larger transport corridor leading to another entity.
  • D. formsTransportCorridorBetween
    Indicates that something creates or constitutes a transportation link or route connecting two locations or entities.
  • E. typeOfTransportInfrastructure chosen
    Indicates the specific category or kind of transport infrastructure associated with or used in a given context.
  • 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_69ca84d64f6c8190a4ed4e9f5936eda5 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda09ed54c8190a5879e14184cddf4 completed April 1, 2026, 10:47 p.m.
PD Predicate disambiguation batch_69cd03d3b68c81909e570401a891b9f2 completed April 1, 2026, 11:38 a.m.
Created at: March 30, 2026, 8:25 p.m.