Triple
T23853780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asch Building |
E592246
|
entity |
| Predicate | numberOfDeathsInNotableEvent |
P154198
|
FINISHED |
| Object | 146 |
—
|
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: 146 | Statement: [Asch Building, numberOfDeathsInNotableEvent, 146]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfDeathsInNotableEvent Context triple: [Asch Building, numberOfDeathsInNotableEvent, 146]
-
A.
notableDeathTollEvent
Indicates that an event is characterized by causing an unusually large or historically significant number of deaths.
-
B.
casualtiesAssociatedWithEvent
Indicates that certain casualties (deaths or injuries) are linked to, or resulted from, a specific event.
-
C.
notableVictims
Indicates that the object is a person or group who is especially well-known or significant as a victim of the subject.
-
D.
causeOfDeathsCommemorated
Indicates that one entity is the cause of the deaths that are formally remembered or honored by another entity.
-
E.
militaryDeaths
Indicates the number of individuals who died while serving in a military capacity, typically during armed conflict or related operations.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98954748190b39e0ac69e5625f9 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:11 p.m.