Triple
T21048114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y-blokka |
E518500
|
entity |
| Predicate | dateOfEventDamage |
P111853
|
FINISHED |
| Object | 2011-07-22 |
—
|
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: 2011-07-22 | Statement: [Y-blokka, dateOfEventDamage, 2011-07-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfEventDamage Context triple: [Y-blokka, dateOfEventDamage, 2011-07-22]
-
A.
dateOfLoss
Indicates the specific date on which a loss event (such as damage, theft, or other covered incident) occurred.
-
B.
sufferedEventDate
chosen
Indicates the specific date on which an entity experienced or was affected by a particular event.
-
C.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
D.
dateOfAccidentInvestigated
Indicates that a specific accident has been examined or investigated on a particular date.
-
E.
ruptureDate
Indicates the date on which a rupture event (such as a break, burst, or failure) occurs in the relationship between entities.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf5b01481909db49aa5be3846aa |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:34 p.m.