Triple
T36573327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BharatNet |
E902173
|
entity |
| Predicate | backboneFor |
P2565
|
FINISHED |
| Object | e-governance services |
—
|
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: e-governance services | Statement: [BharatNet, backboneFor, e-governance services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backboneFor Context triple: [BharatNet, backboneFor, e-governance services]
-
A.
backboneType
Indicates the structural configuration or category of backbone that characterizes or supports an entity.
-
B.
missionBackboneFor
Indicates that one entity serves as the core supporting structure or essential foundation enabling the mission or primary purpose of another entity.
-
C.
backedFor
Indicates that one entity provides support, endorsement, or backing for another entity, often in a financial, political, or strategic context.
-
D.
isBackboneOf
chosen
Indicates that one entity forms the main supporting structure or central framework upon which another entity fundamentally depends.
-
E.
backboneAreaID
Indicates the identifier of the area or region associated with a backbone (e.g., a primary structural or network backbone).
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.