Triple

T28884331
Position Surface form Disambiguated ID Type / Status
Subject The Junction E732510 entity
Predicate transportationTypeAssociated P1379 FINISHED
Object railways 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: railways | Statement: [The Junction, transportationTypeAssociated, railways]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transportationTypeAssociated
Context triple: [The Junction, transportationTypeAssociated, railways]
  • A. transportAssociated
    Indicates an association between entities where one is involved in, related to, or characterized by the transport or movement of the other.
  • B. transportType chosen
    Indicates the mode or means of transportation used in carrying something or someone from one place to another.
  • C. hasTransportationRelation
    Indicates a relationship in which one entity provides, uses, is connected by, or is otherwise associated with a means or mode of transportation to another entity or location.
  • D. isTransportationType
    Indicates that one entity functions as a mode or category of transportation for the other entity.
  • E. transportRole
    Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
  • 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_69f05b07bdec819080cadfe147aa1f25 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69fd231cab588190ad0953dc8f4af8f2 completed May 7, 2026, 11:41 p.m.
PD Predicate disambiguation batch_69fd1aa3f1c481909fe6e9cab1383551 completed May 7, 2026, 11:05 p.m.
Created at: April 28, 2026, 7:48 a.m.