Triple
T36573324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BharatNet |
E902173
|
entity |
| Predicate | Phase II objective |
P79870
|
FINISHED |
| Object | connect remaining gram panchayats |
—
|
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: connect remaining gram panchayats | Statement: [BharatNet, Phase II objective, connect remaining gram panchayats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Phase II objective Context triple: [BharatNet, Phase II objective, connect remaining gram panchayats]
-
A.
phase2Purpose
chosen
Indicates the specific intended goal, function, or outcome associated with the second phase of a process or project.
-
B.
phaseIIIDescription
Indicates that the entity has a textual description specifically about its Phase III stage in a process, study, or project.
-
C.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
-
D.
phase1Purpose
Indicates that one entity serves as the specific purpose, goal, or intended outcome of the first phase of another entity, process, or project.
-
E.
secondaryGoal
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
- 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_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.