Triple
T25327875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 168 of the Constitution of India |
E635066
|
entity |
| Predicate | mentionsOffice |
P158813
|
FINISHED |
| Object | Governor of the State |
—
|
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: Governor of the State | Statement: [Article 168 of the Constitution of India, mentionsOffice, Governor of the State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsOffice Context triple: [Article 168 of the Constitution of India, mentionsOffice, Governor of the State]
-
A.
officeIs
Indicates that one entity serves as the office or official workplace location of another entity.
-
B.
officeIn
Indicates that one entity has an office located within the premises or jurisdiction of another entity.
-
C.
includedOffice
Indicates that one office is contained within, or forms part of, another office or organizational unit.
-
D.
worksWithOffice
Indicates that an entity collaborates or is professionally associated with a particular office or office-based organization.
-
E.
officeUnder
Indicates that one office is subordinate to, managed by, or organizationally within the authority of another office.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497c1067081908fe9dd5682474352 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 1:30 p.m.