Triple

T688378
Position Surface form Disambiguated ID Type / Status
Subject 40th Street Portal E13334 entity
Predicate isJunctionOf P14465 FINISHED
Object underground trolley tunnel and surface trolley routes 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: underground trolley tunnel and surface trolley routes | Statement: [40th Street Portal, isJunctionOf, underground trolley tunnel and surface trolley routes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isJunctionOf
Context triple: [40th Street Portal, isJunctionOf, underground trolley tunnel and surface trolley routes]
  • A. hasJunctionWith
    Indicates that one entity meets or intersects with another at a shared junction point.
  • B. junctionStation chosen
    Indicates that a station functions as a junction where multiple routes or lines intersect or connect.
  • C. connectsTo
    Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
  • D. isAdjacentTo
    Indicates that one entity is directly next to or bordering another without anything of the same type in between.
  • E. locatedAtIntersectionOf
    Indicates that something is situated at the point where two or more paths, roads, or boundaries cross or meet.
  • 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_69a4933e0f98819097d22766c49b61b8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4a0f55f7481909e052a25bd12d455 completed March 1, 2026, 8:26 p.m.
PD Predicate disambiguation batch_69a49d2048d48190ab99ab59accb6909 completed March 1, 2026, 8:10 p.m.
Created at: March 1, 2026, 7:36 p.m.