Triple
T23439510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Executive of India |
E565356
|
entity |
| Predicate | includesOfficeDefinedInArticle |
P152286
|
FINISHED |
| Object | Article 52 |
—
|
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: Article 52 | Statement: [Union Executive of India, includesOfficeDefinedInArticle, Article 52]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesOfficeDefinedInArticle Context triple: [Union Executive of India, includesOfficeDefinedInArticle, Article 52]
-
A.
includedOffice
Indicates that one office is contained within, or forms part of, another office or organizational unit.
-
B.
relatesToOffice
Indicates that one entity has a connection, association, or relevance to an office, its functions, or its environment.
-
C.
definesOfficeOf
Indicates that one entity specifies or establishes the official role, position, or office associated with another entity.
-
D.
officeInherited
Indicates that one entity holds an office or position as a result of inheriting it from another entity.
-
E.
usedByOffice
Indicates that something is utilized, operated, or employed by an office or office-related entity.
- F. None of above. chosen
Provenance (4 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5de713c8190b35bfa66dddbd5af |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:50 p.m.