Triple
T36433004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Narbonne (719–720) |
E897493
|
entity |
| Predicate | controlledAfterConflictBy |
P21851
|
FINISHED |
| Object | Umayyad Caliphate |
—
|
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: Umayyad Caliphate | Statement: [Siege of Narbonne (719–720), controlledAfterConflictBy, Umayyad Caliphate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledAfterConflictBy Context triple: [Siege of Narbonne (719–720), controlledAfterConflictBy, Umayyad Caliphate]
-
A.
usedAfterConflict
Indicates that one entity is utilized or applied only after a conflict, dispute, or confrontation has occurred.
-
B.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
C.
controlledAfter
chosen
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
D.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another conflict.
-
E.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: May 3, 2026, 4:10 p.m.