Triple

T17725730
Position Surface form Disambiguated ID Type / Status
Subject N9 national route E442455 entity
Predicate connectsCoastalAreaToInland P108869 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: [N9 national route, connectsCoastalAreaToInland, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsCoastalAreaToInland
Context triple: [N9 national route, connectsCoastalAreaToInland, true]
  • A. connectsInlandCityToCoast
    Indicates a relationship where a route, link, or infrastructure connects an inland city to a coastal area or city.
  • B. connectsCoastToBorder
    Indicates a relationship where something (such as a route, feature, or boundary) links a coastal area directly to a national or regional border.
  • C. connectsInlandCommunitiesTo chosen
    Indicates a relationship in which something serves as a link or conduit between inland communities and another place, system, or network.
  • D. connectsCoastalCity
    Indicates a relationship where one entity provides a direct connection or link (such as transport or infrastructure) between coastal cities.
  • E. connectsPeninsulaTo
    Indicates a relationship where a geographic feature or structure links a peninsula to another landmass or area.
  • 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_69d8b9ec79688190b86bdcef85a7b3aa completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e47489c59c8190bbffefad20dc6346 completed April 19, 2026, 6:22 a.m.
PD Predicate disambiguation batch_69e3cde815e08190881972e2d80d151e completed April 18, 2026, 6:31 p.m.
Created at: April 10, 2026, 10:07 a.m.