Triple
T9998945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Private James Francis Ryan |
E197273
|
entity |
| Predicate | survivesWarInNarrative |
P48637
|
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: [Private James Francis Ryan, survivesWarInNarrative, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivesWarInNarrative Context triple: [Private James Francis Ryan, survivesWarInNarrative, true]
-
A.
survivedConflict
chosen
Indicates that an entity continued to live or exist after experiencing and enduring a specific conflict or violent event.
-
B.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
C.
survivedChineseCivilWar
Indicates that an entity lived through and remained alive after the events of the Chinese Civil War.
-
D.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
E.
survivedSecondSinoJapaneseWar
Indicates that the subject continued to live through and beyond the duration of the Second Sino-Japanese 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcc8c78448190a5332f4ff8a7b3dd |
completed | April 2, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:51 p.m.