Triple
T36873344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E12 |
E911278
|
entity |
| Predicate | routeSectionInFinland |
P51005
|
FINISHED |
| Object | Vaasa–Tampere |
—
|
NE NERFINISHED |
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: Vaasa–Tampere | Statement: [European route E12, routeSectionInFinland, Vaasa–Tampere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeSectionInFinland Context triple: [European route E12, routeSectionInFinland, Vaasa–Tampere]
-
A.
routeSectionInSweden
Indicates that a specific route section is located within the geographical boundaries of Sweden.
-
B.
routeSectionInNorway
Indicates that a specific route section is located within the geographical boundaries of Norway.
-
C.
distanceToLappeenranta_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Lappeenranta.
-
D.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
E.
routeRegion
chosen
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
- F. None of above.
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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:13 p.m.