Triple

T28633609
Position Surface form Disambiguated ID Type / Status
Subject Tehran Metro Line 3 E724711 entity
Predicate isMassTransitBackbone P48479 FINISHED
Object yes 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: yes | Statement: [Tehran Metro Line 3, isMassTransitBackbone, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMassTransitBackbone
Context triple: [Tehran Metro Line 3, isMassTransitBackbone, yes]
  • A. isPublicTransportBackboneOf chosen
    Indicates that one transport system serves as the primary structural and functional core of a region’s overall public transportation network.
  • B. isTransport
    Indicates that one entity serves as a means or method for conveying or carrying another entity from one place to another.
  • C. hasParallelTransit
    Indicates that one transit route, service, or segment runs in parallel to another along a similar path or corridor.
  • D. isCombinationBackboneWith
    Indicates a structural relationship where one entity serves as a backbone or core framework that is combined with another entity to form a composite or integrated whole.
  • E. isMajorTransitNode
    Indicates that a location functions as a primary hub in a transportation network, where multiple major routes or services intersect or connect.
  • 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_69f01d8328c48190bc0e5f9b9b848582 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f652a492108190b885b955ce147d3c completed May 2, 2026, 7:38 p.m.
PD Predicate disambiguation batch_69f651aad92c8190b874b3b5f9f64434 completed May 2, 2026, 7:34 p.m.
Created at: April 28, 2026, 4:38 a.m.