Triple
T33832492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miran Shah |
E867139
|
entity |
| Predicate | recentRole |
P268
|
FINISHED |
| Object | focal point in counterinsurgency operations |
—
|
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: focal point in counterinsurgency operations | Statement: [Miran Shah, recentRole, focal point in counterinsurgency operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recentRole Context triple: [Miran Shah, recentRole, focal point in counterinsurgency operations]
-
A.
recentHistory
Indicates that one entity represents the most recent sequence of events, states, or interactions associated with another entity.
-
B.
subsequentRole
Indicates that one role or position is held after, and in succession to, another role or position.
-
C.
currentPrimaryRole
Indicates the role an entity is presently holding as its main or most important function or position.
-
D.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
E.
providedRole
Indicates that one entity has assigned or supplied a specific role or function to another 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700274edc8190a1fc5c3a69aa08d0 |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.