Triple
T2845267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A9 road |
E62567
|
entity |
| Predicate | upgradePlanned |
P4375
|
FINISHED |
| Object | dualling between Perth and Inverness |
—
|
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 between Perth and Inverness | Statement: [A9 road, upgradePlanned, dualling between Perth and Inverness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradePlanned Context triple: [A9 road, upgradePlanned, dualling between Perth and Inverness]
-
A.
plannedUpgrade
chosen
Indicates that an entity has a scheduled or intended improvement or enhancement to be carried out in the future.
-
B.
upgradeGoal
Indicates that an entity has a target or intended improvement to a higher level, version, or state relative to its current condition.
-
C.
upgradePath
Indicates the relationship by which one entity can be improved, enhanced, or transitioned into another, typically more advanced, version or state.
-
D.
upgradeDate
Indicates the date on which an entity was upgraded to a newer or improved version.
-
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.
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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf1b58c88190b45d8c5a76dc52ac |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.