Triple
T31802286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zubayrid regime |
E811772
|
entity |
| Predicate | territorialControlVariedDuring |
P1701
|
FINISHED |
| Object | Second Fitna |
—
|
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: Second Fitna | Statement: [Zubayrid regime, territorialControlVariedDuring, Second Fitna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territorialControlVariedDuring Context triple: [Zubayrid regime, territorialControlVariedDuring, Second Fitna]
-
A.
gainedTerritory
Indicates that one entity has acquired control over additional land or area from another entity or from a neutral state.
-
B.
territorialPower
Indicates that an entity holds governing authority or control over a specific geographic territory.
-
C.
territoryLaterControlledBy
Indicates that a territory was subsequently governed, ruled, or administered by a specified controlling entity after an earlier period.
-
D.
heldTerritory
Indicates that one entity maintained control or possession over a specific territory or geographic area.
-
E.
territorialChange
chosen
Indicates a change in control or ownership of geographic territory from one entity to another, often as a result of political, legal, or military events.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 30, 2026, 11:42 p.m.