Triple

T20459353
Position Surface form Disambiguated ID Type / Status
Subject Berliner Ring E501881 entity
Predicate hasJunctionWith P1018 FINISHED
Object A12 NE NERFINISHED

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: A12 | Statement: [Berliner Ring, hasJunctionWith, A12]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A12
Context triple: [Berliner Ring, hasJunctionWith, A12]
  • A. A12
    The A12 is a major road in England that connects London with East Anglia, serving key towns and cities including Ipswich and Colchester.
  • B. A12
    A12 is a major Swiss motorway that connects the regions of Bern and Fribourg, serving as an important north–south transit corridor.
  • C. A12
    A12 is a major French motorway that forms part of the national autoroute network, connecting the outskirts of Paris with the western regions.
  • D. A13
    A13 is a major Swiss motorway running along the country’s eastern side, providing an important north–south transit route through the Alps.
  • E. A13
    A13 is a major road in England that serves as a key route linking London with areas in south Essex, including Basildon.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

Provenance (2 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_69e0b4ad4940819098cf2ff6413574e5 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e696a4652c8190acf79fa2e285e436 completed April 20, 2026, 9:12 p.m.
Created at: April 16, 2026, 11:33 a.m.