Triple
T27540396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime Minister of Afghanistan |
E695217
|
entity |
| Predicate | usedInRegime |
P55826
|
FINISHED |
| Object | Kingdom of Afghanistan |
—
|
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: Kingdom of Afghanistan | Statement: [Prime Minister of Afghanistan, usedInRegime, Kingdom of Afghanistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRegime Context triple: [Prime Minister of Afghanistan, usedInRegime, Kingdom of Afghanistan]
-
A.
occursInRegime
chosen
Indicates that an event, process, or phenomenon takes place within a specific regime, context, or operating condition.
-
B.
useRegime
Indicates a relationship where a particular method, system, or set of rules is applied or followed in carrying out an action or process.
-
C.
usedByRegimeType
Indicates that something (such as a method, policy, or tool) is employed or implemented by a particular type of political regime.
-
D.
usedInState
Indicates that something is employed, applied, or functions within a particular state or condition.
-
E.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 1:30 p.m.