Triple
T23986846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | النكبة |
E604962
|
entity |
| Predicate | hasCommemorationName |
P154143
|
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: [النكبة, hasCommemorationName, يوم النكبة]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommemorationName Context triple: [النكبة, hasCommemorationName, يوم النكبة]
-
A.
hasCommemorationFunction
Indicates that something serves the role or purpose of commemorating an event, person, group, or concept.
-
B.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
C.
includesCommemoration
Indicates that one entity contains, incorporates, or features a commemoration of another entity, event, or person.
-
D.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
E.
isCommemorationSubject
Indicates that an entity serves as the focus or object of a commemorative act, event, or artifact.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38838f481909a52fccd392a92df |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:36 p.m.