Triple
T15480308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A4 motorway |
E376897
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | A4 |
E907657
|
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: A4 | Statement: [A4 motorway, roadNumber, A4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A4 Context triple: [A4 motorway, roadNumber, A4]
-
A.
A4
chosen
A4 is a major European motorway designation used for important long-distance road routes in several countries.
-
B.
A4
A4 is a major French autoroute that connects Paris to the eastern regions of France and onward toward Germany.
-
C.
A4
A4 is a major west–east arterial road in London that forms part of the primary route between central London, Heathrow Airport, and the west of England.
-
D.
A4
A4 is a major Swiss motorway that connects the Zurich region with central and northern Switzerland, facilitating both national and international traffic.
-
E.
4A
4A is a line of the Santiago Metro in Chile that serves as a supplementary route connecting parts of Line 2 and Line 4 across the city’s southern sector.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f8a77a081909f12f13660452f4a |
completed | April 16, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff2d0d6ef0819091623de2888a7101 |
completed | May 9, 2026, 12:48 p.m. |
Created at: April 10, 2026, 3:34 a.m.