Triple
T36573315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BharatNet |
E902173
|
entity |
| Predicate | targetSpeed |
P125449
|
FINISHED |
| Object | high-speed broadband |
—
|
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: high-speed broadband | Statement: [BharatNet, targetSpeed, high-speed broadband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetSpeed Context triple: [BharatNet, targetSpeed, high-speed broadband]
-
A.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
B.
baseSpeed
Indicates the default or starting rate at which an entity moves or operates before any modifications or adjustments.
-
C.
plannedSpeed
chosen
Indicates the intended or target speed that an entity is expected or scheduled to maintain, rather than its actual current speed.
-
D.
triggerSpeed
Indicates the speed or rate at which a triggering event or condition is activated or occurs.
-
E.
currentSpeed
Indicates the present rate at which an entity is moving over time.
- 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_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
Created at: May 3, 2026, 4:11 p.m.