Triple
T847984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bockscar |
E18318
|
entity |
| Predicate | survivedWar |
P5939
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bockscar, survivedWar, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivedWar Context triple: [Bockscar, survivedWar, true]
-
A.
survivedChineseCivilWar
Indicates that an entity lived through and remained alive after the events of the Chinese Civil War.
-
B.
survivedSecondSinoJapaneseWar
Indicates that the subject continued to live through and beyond the duration of the Second Sino-Japanese War.
-
C.
survivedEvent
chosen
Indicates that an entity continued to live or exist after experiencing and not being destroyed or killed by a particular event.
-
D.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
E.
prisonersOfWar
Indicates a relationship where certain individuals are held in custody by an enemy during an armed conflict as prisoners of war.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac1e41748190a21cd1ce5ebcb8ff |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa807adc8190ad808a573cf8e923 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.