Triple
T38102049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fall of Sidon (1291) |
E951407
|
entity |
| Predicate | militaryActionBy |
P59039
|
FINISHED |
| Object | Mamluk army |
—
|
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: Mamluk army | Statement: [Fall of Sidon (1291), militaryActionBy, Mamluk army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryActionBy Context triple: [Fall of Sidon (1291), militaryActionBy, Mamluk army]
-
A.
militaryActivity
Indicates that an entity is engaged in, associated with, or affected by actions, operations, or preparations conducted by armed forces.
-
B.
coordinatesMilitaryOperationsOf
Indicates having authority to plan, direct, and manage the military operations carried out by another entity.
-
C.
militaryCampaignOf
chosen
Indicates a relationship where a specific military campaign is conducted by, initiated by, or belongs to a particular military force, state, or commander.
-
D.
militaryEventMentionedIn
Indicates that a specific military event is referenced or discussed within a particular document, text, or source.
-
E.
militaryOperationName
Indicates the specific named military operation associated with an action, event, or entity.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:21 p.m.