Triple
T20477660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarkaryavah |
E502360
|
entity |
| Predicate | organizationStructureRole |
P118631
|
FINISHED |
| Object | top executive position in RSS |
—
|
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: top executive position in RSS | Statement: [Sarkaryavah, organizationStructureRole, top executive position in RSS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationStructureRole Context triple: [Sarkaryavah, organizationStructureRole, top executive position in RSS]
-
A.
managementRole
Indicates that one entity holds a managerial or supervisory role with authority and responsibility over another entity.
-
B.
hasStructureRole
chosen
Indicates that an entity serves a specific functional or positional role within a larger structure or organizational arrangement.
-
C.
keyOrganizationRole
Indicates that an organization holds a primary or defining role in relation to another entity or activity.
-
D.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
E.
parentOrganizationRole
Indicates that an organization holds a specific role or position within a larger parent organization.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69966b9748190a5296d8ab03c07a1 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.