Triple
T3867481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A1(M) motorway |
E91895
|
entity |
| Predicate | partiallyUpgradedFrom |
P21068
|
FINISHED |
| Object | former A1 dual 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: former A1 dual carriageway sections | Statement: [A1(M) motorway, partiallyUpgradedFrom, former A1 dual carriageway sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyUpgradedFrom Context triple: [A1(M) motorway, partiallyUpgradedFrom, former A1 dual carriageway sections]
-
A.
partlyUpgradedTo
chosen
Indicates that an entity has undergone an incomplete or partial upgrade to another specified state, version, or configuration.
-
B.
upgradesFrom
Indicates that one entity is a newer or improved version that replaces or enhances another entity.
-
C.
openedAsUpgradeOf
Indicates that one entity was opened specifically as an upgraded or improved replacement of another entity.
-
D.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
E.
plannedUpgrade
Indicates that an entity has a scheduled or intended improvement or enhancement to be carried out in the future.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3cc1a88190924125a86f72fd5b |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.