Triple
T13118946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E75 |
E311673
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | E75 |
E966487
|
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: E75 | Statement: [European route E75, roadNumber, E75]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: E75 Context triple: [European route E75, roadNumber, E75]
-
A.
E75
chosen
E75 is a major north–south European route running from northern Norway through central Europe to Greece, forming part of the international E-road network.
-
B.
E75
The E75 is a Nokia Eseries smartphone known for its slide-out QWERTY keyboard and business-oriented features.
-
C.
E70
E70 is a Nokia Eseries smartphone known for its fold-out full QWERTY keyboard and business-oriented features.
-
D.
E70
E70 is BMW's internal model designation for the second-generation X5 mid-size luxury SUV produced from 2006 to 2013.
-
E.
S75
S75 is a line of the Berlin S-Bahn urban rail network serving routes within the Berlin metropolitan area.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98182011c8190a504678affbb7787 |
completed | April 10, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6e284c3c881909d65e2ba89fbe7af |
completed | May 3, 2026, 5:52 a.m. |
Created at: April 9, 2026, 9:06 p.m.