Triple
T6568779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhu al-Qadah |
E155379
|
entity |
| Predicate | warfareRuling |
P71917
|
FINISHED |
| Object | warfare traditionally forbidden |
—
|
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: warfare traditionally forbidden | Statement: [Dhu al-Qadah, warfareRuling, warfare traditionally forbidden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warfareRuling Context triple: [Dhu al-Qadah, warfareRuling, warfare traditionally forbidden]
-
A.
battleDuringRule
Indicates that a battle or military conflict occurred during the period when a particular entity (typically a ruler or regime) held power.
-
B.
warName
Indicates the specific name or title assigned to a particular war or armed conflict.
-
C.
concludedWar
Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
-
D.
warCustom
Indicates a relationship in which one party engages in or applies a particular war-related practice, norm, or customary way of conducting warfare toward or involving another.
-
E.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
- F. None of above. chosen
Provenance (4 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_69c688151254819080387f87deab8fa7 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 1:53 p.m.