Triple

T13944584
Position Surface form Disambiguated ID Type / Status
Subject Coimbra-B E335345 entity
Predicate connectsToCityCentreBy P3791 FINISHED
Object shuttle trains to Coimbra-A 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: shuttle trains to Coimbra-A | Statement: [Coimbra-B, connectsToCityCentreBy, shuttle trains to Coimbra-A]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsToCityCentreBy
Context triple: [Coimbra-B, connectsToCityCentreBy, shuttle trains to Coimbra-A]
  • A. cityCentreAccess
    Indicates whether an entity has access to, or is reachable within, the central area of a city.
  • B. connectsToUrbanCenter
    Indicates that one entity has a direct or functional linkage to an urban center, such as through infrastructure, services, or regular interaction.
  • C. connectsDowntownTo
    Indicates a relationship where one location, route, or service provides a direct connection or access to a downtown area.
  • D. hasPublicTransportConnection chosen
    Indicates that there is an available public transportation link or service connecting the related entities.
  • E. connectsCityTo
    Indicates a relationship in which a route, infrastructure, or link joins one city to another, enabling connection or interaction between them.
  • 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_69d81c6081b88190b53e317c3370c8fe completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e0f6f3c8190a64058b732b0ac52 completed April 14, 2026, 12:07 p.m.
PD Predicate disambiguation batch_69de05a3ccf88190b45c742db483fa08 completed April 14, 2026, 9:15 a.m.
Created at: April 9, 2026, 10:17 p.m.