Triple
T26112861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Members of the Chhattisgarh Legislative Assembly |
E658744
|
entity |
| Predicate | takeOathBefore |
P11710
|
FINISHED |
| Object | Governor of Chhattisgarh |
—
|
NE NERFINISHED |
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 Chhattisgarh | Statement: [Members of the Chhattisgarh Legislative Assembly, takeOathBefore, Governor of Chhattisgarh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takeOathBefore Context triple: [Members of the Chhattisgarh Legislative Assembly, takeOathBefore, Governor of Chhattisgarh]
-
A.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
B.
oathTakenBy
Indicates that an oath or formal promise has been made by a specific entity.
-
C.
oathSwornBefore
chosen
Indicates that an oath or solemn promise has been formally declared in the presence of a specified person, group, or authority.
-
D.
takesVowsOf
Indicates that an entity formally commits to specific vows, promises, or oaths, typically within a religious, ceremonial, or institutional context.
-
E.
administersOathTo
Indicates that one entity formally gives or conducts an oath that another entity takes.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6077d48408190ad851e002499bbdb |
completed | May 2, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:03 p.m.