Triple
T23435583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A303 |
E563449
|
entity |
| Predicate | upgradePlans |
P152267
|
FINISHED |
| Object | dualling of remaining single-carriageway sections |
—
|
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: dualling of remaining single-carriageway sections | Statement: [A303, upgradePlans, dualling of remaining single-carriageway sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradePlans Context triple: [A303, upgradePlans, dualling of remaining single-carriageway sections]
-
A.
upgradePlan
Indicates that one entity changes another entity’s plan to a higher or more advanced level.
-
B.
upgradeOption
Indicates that one entity serves as a possible improved or higher-level alternative to another entity.
-
C.
upgradePrice
Indicates the monetary cost required to move from a current version, tier, or level of something to a higher or more advanced one.
-
D.
upgradeType
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
E.
upgradeProgram
Indicates that one entity improves, enhances, or replaces another entity’s program with a more advanced or updated version.
- F. None of above. chosen
Provenance (4 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5dbdf248190a09e971f2718d01f |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:50 p.m.