Triple

T23554931
Position Surface form Disambiguated ID Type / Status
Subject St. Teresa E578157 entity
Predicate hasAdjacentStationOnLine2 P131439 FINISHED
Object other Line 2 stations in Shubra corridor 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: other Line 2 stations in Shubra corridor | Statement: [St. Teresa, hasAdjacentStationOnLine2, other Line 2 stations in Shubra corridor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAdjacentStationOnLine2
Context triple: [St. Teresa, hasAdjacentStationOnLine2, other Line 2 stations in Shubra corridor]
  • A. hasAdjacentStationOnLine1
    Indicates that one station is directly next to another station along Line 1 in the network.
  • B. hasAdjacentStationOnLine 2 chosen
    Indicates that one station is directly next to another station along Line 2 in the network.
  • C. hasAdjacentStationOnLine12
    Indicates that one station is directly next to another station along transit line 12, with no other stations in between on that line.
  • D. hasAdjacentStationOnLine 5
    Indicates that one station is directly next to another station along line 5, with no other stations in between on that line.
  • E. hasAdjacentStationOnLine 7bis
    Indicates that one station is directly next to another station along metro line 7bis.
  • 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_69e245fa93448190919cb04534560542 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1aed253788190ba75109af0e91b37 completed April 29, 2026, 7:10 a.m.
PD Predicate disambiguation batch_69f118afabd88190bd88f49597d120e8 completed April 28, 2026, 8:29 p.m.
Created at: April 17, 2026, 6:12 p.m.