Triple
T10679083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The End of the War: Starting Home |
E251695
|
entity |
| Predicate | creatorMilitaryService |
P38925
|
FINISHED |
| Object | World War I veteran |
—
|
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: World War I veteran | Statement: [The End of the War: Starting Home, creatorMilitaryService, World War I veteran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorMilitaryService Context triple: [The End of the War: Starting Home, creatorMilitaryService, World War I veteran]
-
A.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
-
B.
militaryBackground
chosen
Indicates that an entity has prior or current experience, service, or training in a military organization.
-
C.
mainCharacterMilitaryService
Indicates that the main character has served or is serving in the military, capturing their involvement in formal armed forces service.
-
D.
hadMilitaryPost
Indicates that an entity held an official position or assignment within a military organization.
-
E.
militaryUnitTypeServed
Indicates that an entity served in, or was a member of, a specific type of military unit.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fb9684e48190b2786823723cde6c |
completed | April 9, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.