Triple
T8811165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saraikistan (proposed region) |
E209661
|
entity |
| Predicate | demandsInclude |
P7686
|
FINISHED |
| Object | separate provincial assembly |
—
|
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: separate provincial assembly | Statement: [Saraikistan (proposed region), demandsInclude, separate provincial assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demandsInclude Context triple: [Saraikistan (proposed region), demandsInclude, separate provincial assembly]
-
A.
orderIncludes
Indicates that a particular order contains or comprises the specified item(s) or component(s).
-
B.
demands
chosen
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
-
C.
reasoningIncludes
Indicates that a reasoning process or argument explicitly incorporates or makes use of the referenced element as one of its components or steps.
-
D.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
E.
distributionIncludes
Indicates that a distribution or release of something contains or encompasses the specified item or component.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fed18f8819087b0282bf8c4208c |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.