Triple
T30213083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Coubre memorial rally |
E768122
|
entity |
| Predicate | hasVictimCountCommemorated |
P4086
|
FINISHED |
| Object | over 70 dead |
—
|
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: over 70 dead | Statement: [La Coubre memorial rally, hasVictimCountCommemorated, over 70 dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVictimCountCommemorated Context triple: [La Coubre memorial rally, hasVictimCountCommemorated, over 70 dead]
-
A.
hasVictimsCount
Indicates the number of victims associated with a particular event, action, or entity.
-
B.
memorializesVictimsFrom
Indicates that something serves as a memorial specifically honoring victims originating from a particular place or event.
-
C.
numberOfCommemoratedPersons
chosen
Indicates the count of distinct persons who are commemorated or honored in a given context or entity.
-
D.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
E.
causeOfDeathsCommemorated
Indicates that one entity is the cause of the deaths that are formally remembered or honored by another 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 29, 2026, 7:33 p.m.