Triple
T25259789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chairperson of Prasar Bharati |
E633270
|
entity |
| Predicate | isPublicServiceRole |
P10788
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chairperson of Prasar Bharati, isPublicServiceRole, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublicServiceRole Context triple: [Chairperson of Prasar Bharati, isPublicServiceRole, true]
-
A.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
B.
hasPublicSpaceRole
Indicates that an entity holds a specific role, function, or responsibility within a public space.
-
C.
isKeyRole
Indicates that an entity holds a primary or critically important role within a given context or structure.
-
D.
isNonProfitRole
Indicates that a role or position is associated with a nonprofit organization or activity rather than a for-profit context.
-
E.
hasPublicAuthorityType
chosen
Indicates that an entity possesses a specific type or category of public authority status or role.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4839220bc8190a398032c59943f98 |
completed | May 1, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:13 p.m.