Triple
T4198446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sur Empire |
E86007
|
entity |
| Predicate | majorRoadProject |
P49938
|
FINISHED |
| Object | Grand Trunk Road improvements |
—
|
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: Grand Trunk Road improvements | Statement: [Sur Empire, majorRoadProject, Grand Trunk Road improvements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRoadProject Context triple: [Sur Empire, majorRoadProject, Grand Trunk Road improvements]
-
A.
majorConstructionUnder
Indicates that a location or structure is currently undergoing significant construction work or large-scale building activity.
-
B.
majorConstruction
chosen
Indicates a relationship where a construction project is large-scale, significant, or of primary importance in scope, impact, or resources.
-
C.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
D.
notableRailwayProject
Indicates that the subject is recognized for involvement in a significant or prominent railway-related project.
-
E.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0360bc8081908ceb2483eef89174 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:48 p.m.