Triple
T22155240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N35 road |
E547517
|
entity |
| Predicate | hasUpgradedSections |
P107430
|
FINISHED |
| Object | dual carriageway near Zwolle |
—
|
LITERAL 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: dual carriageway near Zwolle | Statement: [N35 road, hasUpgradedSections, dual carriageway near Zwolle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpgradedSections Context triple: [N35 road, hasUpgradedSections, dual carriageway near Zwolle]
-
A.
hasElevatedSections
chosen
Indicates that one entity contains or features parts that are raised or elevated relative to its other sections.
-
B.
hasUpgrade
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
C.
hasUpgradeProject
Indicates that an entity is associated with a project whose purpose is to improve, enhance, or modernize that entity.
-
D.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
E.
hasUpgradeSystem
Indicates that an entity includes or is equipped with a system for performing upgrades or enhancements.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f7d034819092ecf9682e549c9a |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.