Triple
T13084639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essingeleden |
E310298
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | E20 |
E521500
|
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: E20 | Statement: [Essingeleden, connectsTo, E20]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: E20 Context triple: [Essingeleden, connectsTo, E20]
-
A.
E20
chosen
E20 is a major trans-European route running west–east across several countries from Ireland through the United Kingdom and northern Europe to Russia.
-
B.
E 200
The E 200 is a Mercedes-Benz E-Class executive sedan variant known for its balance of comfort, technology, and efficient performance.
-
C.
E22
E22 is a major European route that forms part of the international E-road network, linking multiple countries across Europe.
-
D.
E21
E21 is the internal designation for the first generation of the BMW 3 Series compact executive car, produced in the 1970s and early 1980s.
-
E.
E10
E10 is the internal BMW chassis code for the classic 02 Series compact sports sedans produced in the late 1960s and 1970s.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981361e8c819099376435aa3a7aa3 |
completed | April 10, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d61060188190911eb3e135dc25ac |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 9:02 p.m.