Triple
T10249550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E50 |
E240302
|
entity |
| Predicate | countryCode |
P208
|
FINISHED |
| Object | E50 |
E822155
|
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: E50 | Statement: [European route E50, countryCode, E50]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: E50 Context triple: [European route E50, countryCode, E50]
-
A.
E50
chosen
E50 is a major trans-European road corridor that spans multiple countries, facilitating long-distance east–west travel and trade across the continent.
-
B.
E5
E5 is the IATA airline designator assigned to Air Arabia Egypt, a low-cost carrier based in Egypt.
-
C.
E53
E53 is the internal BMW designation for the first-generation BMW X5 mid-size luxury SUV produced from 1999 to 2006.
-
D.
E35
E35 is a major north–south European route running from Amsterdam in the Netherlands to Rome in Italy, passing through Germany and Switzerland.
-
E.
E20
E20 is a major trans-European route running west–east across several countries from Ireland through the United Kingdom and northern Europe to Russia.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23c4cd88190b99e65a074b68d6b |
completed | April 7, 2026, 9:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6f7b66c6881908b432fbdd5ecf11e |
completed | April 9, 2026, 12:49 a.m. |
Created at: April 6, 2026, 11:28 a.m.