Triple
T36573138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telecom Regulatory Authority of India |
E902169
|
entity |
| Predicate | hasSubsidiaryBody |
P747
|
FINISHED |
| Object | Telecom Disputes Settlement and Appellate Tribunal |
—
|
NE NERFINISHED |
How this triple was built (1 step)
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: Telecom Disputes Settlement and Appellate Tribunal | Statement: [Telecom Regulatory Authority of India, hasSubsidiaryBody, Telecom Disputes Settlement and Appellate Tribunal]
Provenance (2 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_69f7c2a296c0819086b0f34fcdcebc74 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.