Triple

T12007207
Position Surface form Disambiguated ID Type / Status
Subject Série 4000 E285810 entity
Predicate primaryRoute P6298 FINISHED
Object Lisbon–Braga E962085 NE 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: Lisbon–Braga | Statement: [Série 4000, primaryRoute, Lisbon–Braga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lisbon–Braga
Context triple: [Série 4000, primaryRoute, Lisbon–Braga]
  • A. Lisbon–Guimarães
    Lisbon–Guimarães is a major intercity rail route in Portugal connecting the capital Lisbon with the historic northern city of Guimarães.
  • B. Lisbon–Porto
    Lisbon–Porto is the main intercity rail corridor in Portugal, linking the capital Lisbon with the northern city of Porto.
  • C. Lisbon–Braga route chosen
    The Lisbon–Braga route is a major intercity rail corridor in Portugal linking the capital Lisbon with the northern city of Braga.
  • D. Lisbon–Faro
    Lisbon–Faro is a major intercity rail corridor in Portugal linking the capital Lisbon with the southern coastal city of Faro in the Algarve region.
  • E. Braga
    Braga is a historic city in northern Portugal known for its rich religious heritage, baroque architecture, and status as a regional cultural and educational center.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6ab45a368819084fce08bf0dc3705 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903c5cfc08190821e4b2940c51416 completed April 10, 2026, 2:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69f62a784b3c81909a2841f3d6b4c475 completed May 2, 2026, 4:46 p.m.
Created at: April 8, 2026, 9:46 p.m.