Triple

T6786090
Position Surface form Disambiguated ID Type / Status
Subject Santo Domingo Metro E155805 entity
Predicate line1Orientation P42939 FINISHED
Object north–south 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: north–south | Statement: [Santo Domingo Metro, line1Orientation, north–south]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: line1Orientation
Context triple: [Santo Domingo Metro, line1Orientation, north–south]
  • A. lineOrientation chosen
    Indicates the directional alignment or angle of a line relative to a reference frame or axis.
  • B. legOrientation
    Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
  • C. lineType
    Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
  • D. lineStandard
    Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
  • E. lineElement
    Indicates a relationship where something functions as, or is identified as, an element or segment of a line within a larger linear structure or representation.
  • 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_69c6881770fc8190972b2906390380f5 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d28f043081909a9a9ab635785933 completed March 27, 2026, 6:55 p.m.
PD Predicate disambiguation batch_69c6d0979ce0819094678896da4e3169 completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:14 p.m.