Triple

T681217
Position Surface form Disambiguated ID Type / Status
Subject Grayshott E13184 entity
Predicate locatedNear P294 FINISHED
Object A3 road E18328 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: A3 road | Statement: [Grayshott, locatedNear, A3 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A3 road
Context triple: [Grayshott, locatedNear, A3 road]
  • A. A3 road chosen
    The A3 road is a major trunk route in England that connects London to Portsmouth, passing through counties such as Surrey.
  • B. 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.
  • C. 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.
  • D. A30 road
    The A30 road is a major trunk route in southern England that runs from London through counties including Surrey toward the southwest.
  • E. A31 road
    The A31 road is a major route in southern England that connects Guildford in Surrey to Dorset, forming part of an important east–west corridor between London and the south coast.
  • 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_69a4933d3bf88190972041cd8cf143b9 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4a06e294c8190873116a3253e04f9 completed March 1, 2026, 8:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69acddf440848190aa5019ffcedd4859 completed March 8, 2026, 2:24 a.m.
Created at: March 1, 2026, 7:36 p.m.