Triple
T26995269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajasthan Public Works Department |
E679964
|
entity |
| Predicate | typeOfRoadsHandled |
P155951
|
FINISHED |
| Object | state highways |
—
|
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: state highways | Statement: [Rajasthan Public Works Department, typeOfRoadsHandled, state highways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRoadsHandled Context triple: [Rajasthan Public Works Department, typeOfRoadsHandled, state highways]
-
A.
typeOfRoadOperated
chosen
Indicates that an entity operates or manages a specific type or category of road.
-
B.
appliesToRoadType
Indicates that a rule, condition, or attribute is specifically relevant or valid for a particular type or category of road.
-
C.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
D.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
E.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 27, 2026, 6:54 a.m.