Triple

T9139916
Position Surface form Disambiguated ID Type / Status
Subject Deportivo 18 de Marzo (via Line 6 corridor, non-immediate) E219297 entity
Predicate transferCorridor P86994 FINISHED
Object Line 6 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: Line 6 corridor | Statement: [Deportivo 18 de Marzo (via Line 6 corridor, non-immediate), transferCorridor, Line 6 corridor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transferCorridor
Context triple: [Deportivo 18 de Marzo (via Line 6 corridor, non-immediate), transferCorridor, Line 6 corridor]
  • A. transferFeature
    Indicates a relationship where a feature, attribute, or capability is moved or reassigned from one entity to another.
  • B. transferComplex
    Indicates the movement or relocation of a multi-component entity or system from one context, location, or state to another.
  • C. formsTransportCorridorBetween
    Indicates that something creates or constitutes a transportation link or route connecting two locations or entities.
  • D. transportCorridor
    Indicates a route or pathway used to move people, goods, or resources between locations.
  • E. transferType
    Indicates the specific method or category of how something is transferred from one entity to another.
  • F. None of above. chosen

Provenance (4 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_69ca83e012288190a5771058adbaabd2 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca8f2537881908956a9b0516e2d49 completed April 1, 2026, 5:11 a.m.
PD Predicate disambiguation batch_69cc6603ce8c8190bf6e8d6754bdec54 completed April 1, 2026, 12:25 a.m.
PDg Predicate description generation batch_69cc6a3d230881909635b2ccea35cedb completed April 1, 2026, 12:43 a.m.
Created at: March 30, 2026, 7:19 p.m.