Triple
T13278812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N106US |
E316262
|
entity |
| Predicate | survivorsDuringEvent |
P11769
|
FINISHED |
| Object | 155 |
—
|
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: 155 | Statement: [N106US, survivorsDuringEvent, 155]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivorsDuringEvent Context triple: [N106US, survivorsDuringEvent, 155]
-
A.
survivingPerpetratorsLaterEvent
Indicates that the perpetrators involved in an earlier event remained alive and present to participate in or be associated with a subsequent event.
-
B.
survivedEvent
Indicates that an entity continued to live or exist after experiencing and not being destroyed or killed by a particular event.
-
C.
placeOfEventSurvived
Indicates the location where an event occurred from which the subject successfully survived.
-
D.
hasSurvivors
chosen
Indicates that one or more entities continue to exist or remain alive after a particular event, condition, or incident.
-
E.
survivingPerpetrators
Indicates that the referenced individuals are perpetrators of an act or event who are still alive following that act or event.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.