Triple
T26471799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Homs (1299) |
E665918
|
entity |
| Predicate | shortTermConsequence |
P812
|
FINISHED |
| Object | Mongol occupation of parts of Syria |
—
|
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: Mongol occupation of parts of Syria | Statement: [Battle of Homs (1299), shortTermConsequence, Mongol occupation of parts of Syria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shortTermConsequence Context triple: [Battle of Homs (1299), shortTermConsequence, Mongol occupation of parts of Syria]
-
A.
unexpectedConsequenceOf
Indicates that one event, action, or condition occurs as an unforeseen or unintended result of another.
-
B.
consequenceInText
Indicates that one event, action, or state is presented in the text as a consequence or result of another.
-
C.
narrativeConsequence
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
-
D.
significantEventConsequence
Indicates that one event leads to an important or impactful consequence for another event, state, or entity.
-
E.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 12:20 a.m.