Triple
T16135047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | نصب الشهيد |
E391501
|
entity |
| Predicate | يرمز_إلى |
P111245
|
FINISHED |
| Object | الشهداء العراقيين |
—
|
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: الشهداء العراقيين | Statement: [نصب الشهيد, يرمز_إلى, الشهداء العراقيين]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يرمز_إلى Context triple: [نصب الشهيد, يرمز_إلى, الشهداء العراقيين]
-
A.
hasIronicMeaning
Indicates that something conveys a meaning opposite to or incongruent with its literal expression, creating an ironic effect.
-
B.
ייחוס
chosen
Indicates an attribution or assignment relationship, where a property, role, or characteristic is ascribed from one entity to another.
-
C.
euphemisticReferenceTo
Indicates that one expression is used as a milder or less direct way of referring to another, often to soften or obscure its impact.
-
D.
usesDoubleEntendre
Indicates that one entity employs language or expressions with a double meaning, often to convey a hidden or suggestive message alongside a literal one.
-
E.
ذُكر_في
Indicates that an entity is mentioned or referenced within another entity, such as a text, document, or source.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a04666c819091f36c5a2497d2e7 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.