Triple
T20965077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murid War |
E516344
|
entity |
| Predicate | insurgentPoliticalStructure |
P32429
|
FINISHED |
| Object | Imamate |
—
|
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: Imamate | Statement: [Murid War, insurgentPoliticalStructure, Imamate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insurgentPoliticalStructure Context triple: [Murid War, insurgentPoliticalStructure, Imamate]
-
A.
rebelInstitution
chosen
Indicates that an institution actively resists, opposes, or defies an established authority, system, or governing power.
-
B.
insurgentSupporter
Indicates that one entity supports, assists, or aligns with an insurgent group or insurgent activities.
-
C.
associatedPoliticalSystem
Indicates that there exists a political system with which the subject is formally or conceptually connected.
-
D.
initialPoliticalStructure
Indicates the original or starting form of political organization or governance that an entity has before any subsequent changes or developments.
-
E.
inGovernmentStructure
Indicates that one entity is part of, belongs to, or is included within the organizational or institutional framework of a government.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb72ef4c8190bebdd2cef3c2148c |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:32 p.m.