Triple
T25258702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Border Roads Organisation |
E633243
|
entity |
| Predicate | typeOfRoadsBuilt |
P1019
|
FINISHED |
| Object | national highways in strategic sectors |
—
|
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: national highways in strategic sectors | Statement: [Border Roads Organisation, typeOfRoadsBuilt, national highways in strategic sectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRoadsBuilt Context triple: [Border Roads Organisation, typeOfRoadsBuilt, national highways in strategic sectors]
-
A.
numberOfRoadways
Indicates the count of distinct roadways associated with or present at a given entity or location.
-
B.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
C.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
D.
roadBuiltFor
Indicates that a road was constructed specifically to serve, provide access to, or support the use or needs of a particular entity.
-
E.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 21, 2026, 1:13 p.m.