Triple
T15203449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A66 road |
E363323
|
entity |
| Predicate | upgradePlan |
P117111
|
FINISHED |
| Object | full dualling between M6 and A1(M) |
—
|
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: full dualling between M6 and A1(M) | Statement: [A66 road, upgradePlan, full dualling between M6 and A1(M)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradePlan Context triple: [A66 road, upgradePlan, full dualling between M6 and A1(M)]
-
A.
upgradeType
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
B.
upgradeProgram
Indicates that one entity improves, enhances, or replaces another entity’s program with a more advanced or updated version.
-
C.
upgradeOption
Indicates that one entity serves as a possible improved or higher-level alternative to another entity.
-
D.
upgradePath
Indicates the relationship by which one entity can be improved, enhanced, or transitioned into another, typically more advanced, version or state.
-
E.
upgradeProject
Indicates performing actions that improve or enhance an existing project, typically by updating its components, capabilities, or quality.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b693a48190a6230b7b52bc8cd3 |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97ee9d881908711dbe12a55283c |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:10 a.m.