Triple

T1927636
Position Surface form Disambiguated ID Type / Status
Subject A14 road E40867 entity
Predicate hasJunctionWith P1018 FINISHED
Object A1 road E31643 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: A1 road | Statement: [A14 road, hasJunctionWith, A1 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A1 road
Context triple: [A14 road, hasJunctionWith, A1 road]
  • A. A1 road chosen
    The A1 road is a major north–south trunk route in England that forms part of the historic Great North Road, linking London with Edinburgh via numerous towns and junctions.
  • B. A11 road
    The A11 road is a major trunk route in eastern England that connects London to Norwich, serving as a key transport corridor through counties such as Cambridgeshire, Suffolk, and Norfolk.
  • C. A10 road
    The A10 road is a major north–south route in England that runs from London through Hertfordshire and beyond, connecting several towns and cities along its length.
  • D. A4 road
    The A4 road is a major historic route in England that runs west from central London through key cities such as Reading, Bath, and Bristol toward Avonmouth.
  • E. A2 road
    The A2 road is a major route in southeast England connecting London to the port of Dover and forming part of a key corridor to mainland Europe.
  • 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_69a8864711648190b07bed24ed76258e completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb263cdb8819084d0bda98a2a71e0 completed March 7, 2026, 5:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69b6130aaa7081908956e2db62005b92 completed March 15, 2026, 2:01 a.m.
Created at: March 4, 2026, 7:35 p.m.