Triple
T29693784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girton interchange |
E751283
|
entity |
| Predicate | upgradeAssociatedWith |
P168774
|
FINISHED |
| Object | A14 Cambridge to Huntingdon improvement scheme |
—
|
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: A14 Cambridge to Huntingdon improvement scheme | Statement: [Girton interchange, upgradeAssociatedWith, A14 Cambridge to Huntingdon improvement scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradeAssociatedWith Context triple: [Girton interchange, upgradeAssociatedWith, A14 Cambridge to Huntingdon improvement scheme]
-
A.
upgradeStatus
Indicates the current state or progress of an upgrade process applied to an entity.
-
B.
upgradeType
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
C.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
D.
upgradeFor
Indicates that one entity serves as an improved or enhanced replacement for another entity.
-
E.
upgradeProgramFundedBy
Indicates that the financial resources for an upgrade program are provided or sponsored by a particular funding entity.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67805551c81909e016ae9e3031076 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 28, 2026, 7:18 p.m.