Triple
T15838027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Damascus (1148) |
E384031
|
entity |
| Predicate | reasonForRetreat |
P23193
|
FINISHED |
| Object | strong Muslim resistance |
—
|
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: strong Muslim resistance | Statement: [Siege of Damascus (1148), reasonForRetreat, strong Muslim resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRetreat Context triple: [Siege of Damascus (1148), reasonForRetreat, strong Muslim resistance]
-
A.
retreatCause
chosen
Indicates that one event, condition, or factor serves as the reason or trigger for a retreat by an entity.
-
B.
eraOfMajorRetreat
Indicates a time period during which a significant withdrawal, decline, or pullback of something (such as forces, influence, or presence) occurred.
-
C.
wasPoliticalRetreatOf
Indicates that one entity served as a political retreat or refuge location for another entity.
-
D.
impactOfRetreat
Indicates the effects or consequences that a retreat has on relevant entities, conditions, or outcomes.
-
E.
reasonForScuttling
Indicates the specific cause or motivation that led to a vessel being deliberately scuttled.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e3d48c8190ad0d0af89d062101 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.