Triple

T26211767
Position Surface form Disambiguated ID Type / Status
Subject Tokyo Metro Namboku Line at Nagatacho E655508 entity
Predicate connectedByPassageTo P156541 FINISHED
Object Tokyo Metro Yurakucho Line at Nagatacho 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: Tokyo Metro Yurakucho Line at Nagatacho | Statement: [Tokyo Metro Namboku Line at Nagatacho, connectedByPassageTo, Tokyo Metro Yurakucho Line at Nagatacho]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectedByPassageTo
Context triple: [Tokyo Metro Namboku Line at Nagatacho, connectedByPassageTo, Tokyo Metro Yurakucho Line at Nagatacho]
  • A. connectedByStraitTo
    Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
  • B. linkedByCorridor chosen
    Indicates that two locations are directly connected to each other by a corridor.
  • C. partlyConnectedBy
    Indicates that two entities are linked or joined by something in an incomplete, partial, or not fully continuous way.
  • D. relatedPass
    Indicates that one pass is associated with or connected to another pass in some relevant way.
  • E. linkedByStructure
    Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
  • 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_69ee5b49adb4819086545280d4ef6337 completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f7308a096081909d66a56f3c926806 completed May 3, 2026, 11:24 a.m.
PD Predicate disambiguation batch_69f72a00c5f081908b6539d15baf4e12 completed May 3, 2026, 10:57 a.m.
Created at: April 26, 2026, 8:52 p.m.