Triple

T12771677
Position Surface form Disambiguated ID Type / Status
Subject Linha da Beira Baixa E305260 entity
Predicate inlandLine P848 FINISHED
Object true 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: true | Statement: [Linha da Beira Baixa, inlandLine, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inlandLine
Context triple: [Linha da Beira Baixa, inlandLine, true]
  • A. terminusInland
    Indicates that something ends, concludes, or has its final point within an inland area rather than at a coast or shoreline.
  • B. connectsInlandCityToCoast
    Indicates a relationship where a route, link, or infrastructure connects an inland city to a coastal area or city.
  • C. locatedInland
    Indicates that something is situated away from the coast or shoreline, within the interior of a land area.
  • D. railwayLine chosen
    Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
  • E. isInlandFrom
    Indicates that one place lies away from the coast, further toward the interior of the land, relative to another place.
  • 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_69d7bdf2b43c819098ae5aa68e61ea58 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96df5b68481908a5d40516b09be52 completed April 10, 2026, 9:39 p.m.
PD Predicate disambiguation batch_69d96409739881909174ba005a986cb5 completed April 10, 2026, 8:56 p.m.
Created at: April 9, 2026, 5:28 p.m.