Triple
T38624750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | van Breda family |
E936975
|
entity |
| Predicate | survivorOf2015Attack |
P132335
|
FINISHED |
| Object | Henri van Breda |
—
|
NE NERFINISHED |
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: Henri van Breda | Statement: [van Breda family, survivorOf2015Attack, Henri van Breda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivorOf2015Attack Context triple: [van Breda family, survivorOf2015Attack, Henri van Breda]
-
A.
survivorOfAttack
chosen
Indicates that one entity has lived through and remains alive after being subjected to an attack carried out by another entity.
-
B.
survivorsJourney
Indicates the ongoing process or path a survivor takes as they cope with, adapt to, and move forward from a traumatic or life-threatening experience.
-
C.
killedInAttack
Indicates that an entity died as a direct result of a specific attack event.
-
D.
survivingPerpetrators
Indicates that the referenced individuals are perpetrators of an act or event who are still alive following that act or event.
-
E.
survivedDisaster
Indicates that an entity continued to live or exist after experiencing and enduring a disaster.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.