Triple
T27666475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007 state of emergency in Pakistan |
E697240
|
entity |
| Predicate | reasonGivenByGovernment |
P172718
|
FINISHED |
| Object | rising militancy |
—
|
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: rising militancy | Statement: [2007 state of emergency in Pakistan, reasonGivenByGovernment, rising militancy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonGivenByGovernment Context triple: [2007 state of emergency in Pakistan, reasonGivenByGovernment, rising militancy]
-
A.
purposeAsStatedByGovernment
chosen
Indicates that the purpose of something is defined or described according to an official statement or designation made by a government.
-
B.
reasonForGrant
Indicates the justification, purpose, or cause for which a grant is awarded or provided.
-
C.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
D.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
-
E.
reasonForSanctions
Indicates the underlying cause or justification for imposing sanctions on an entity.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 2:38 p.m.