Triple
T24133094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Najm ad-Din Ilghazi ibn Artuq |
E598006
|
entity |
| Predicate | defeatedCommander |
P11263
|
FINISHED |
| Object | Roger of Salerno |
—
|
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: Roger of Salerno | Statement: [Najm ad-Din Ilghazi ibn Artuq, defeatedCommander, Roger of Salerno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defeatedCommander Context triple: [Najm ad-Din Ilghazi ibn Artuq, defeatedCommander, Roger of Salerno]
-
A.
commanderOfDefeatedSide
Indicates that the subject is the military or strategic leader of the side that lost in a particular conflict or battle.
-
B.
defeatedBy
chosen
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
C.
defeatedDespite
Indicates that one entity successfully defeated another entity even though circumstances or expectations suggested that defeat would be unlikely or difficult.
-
D.
capturedCommander
Indicates that one party has taken a military commander from another party into custody or control.
-
E.
surrenderedCommander
Indicates that one commander formally yielded authority or control to another, typically as part of a surrender.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df79bfd08190970ed1b3f14ebc8b |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:26 p.m.