Triple
T5582493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A3 motorway (Switzerland) |
E146670
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | A3 |
E408534
|
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 | Statement: [A3 motorway (Switzerland), roadNumber, A3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A3 Context triple: [A3 motorway (Switzerland), roadNumber, A3]
-
A.
A3
A3 is a major national highway in Zimbabwe that serves as an important route connecting key towns and regions within the country.
-
B.
A3
A3 is the IATA airline designator for Aegean Airlines, the largest Greek airline and a member of the Star Alliance.
-
C.
A3
chosen
A3 is a major Swiss motorway that runs across the country’s north, connecting key cities and regions as part of the national highway network.
-
D.
A3
A3 is a major German autobahn that runs across several federal states, serving as an important east–west transport corridor.
-
E.
3A
3A is a highway designation used for several auxiliary or alternate routes of U.S. Route 3 and related highways in New England.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0208333f08190bf0049b6bdd280f5 |
completed | March 22, 2026, 5:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0285e7bc08190bd5a08c50679e9d9 |
completed | March 22, 2026, 5:35 p.m. |
Created at: March 22, 2026, 3:37 p.m.