Triple
T15175576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Highway 66 |
E362598
|
entity |
| Predicate | underUpgradation |
P4375
|
FINISHED |
| Object | four-laning on several stretches |
—
|
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: four-laning on several stretches | Statement: [National Highway 66, underUpgradation, four-laning on several stretches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underUpgradation Context triple: [National Highway 66, underUpgradation, four-laning on several stretches]
-
A.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
B.
upgradeType
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
C.
underwentUpgrade
Indicates that an entity has experienced an improvement or enhancement process that changed it to a newer or more advanced state.
-
D.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
E.
plannedUpgrade
chosen
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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0066236d481909e8ac47f496861ad |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.