Triple
T1805054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speaker of the Lok Sabha |
E40201
|
entity |
| Predicate | precedenceOrderInIndia |
P8140
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Speaker of the Lok Sabha, precedenceOrderInIndia, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedenceOrderInIndia Context triple: [Speaker of the Lok Sabha, precedenceOrderInIndia, high]
-
A.
orderPrecedenceWithinIndia
Indicates the relative ranking or priority of entities in terms of legal or administrative precedence within the jurisdiction of India.
-
B.
rankInIndianOrderOfPrecedence
chosen
Indicates the formal position or level an office or individual holds within the official Indian Order of Precedence hierarchy.
-
C.
orderPrecedenceInCanada
Indicates the relative legal or procedural priority that one item holds over another specifically within the Canadian context.
-
D.
rankByLengthInIndia
Indicates an ordering of items based on their length specifically within the context or boundaries of India.
-
E.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
- 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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba67721788190951beae25e885457 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61d514c081908197ac1f7c7d7a88 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.