Triple
T38675370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian War Memorials Fund |
E943723
|
entity |
| Predicate | theatreOfWarDocumented |
P710
|
FINISHED |
| Object | Western Front |
—
|
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: Western Front | Statement: [Canadian War Memorials Fund, theatreOfWarDocumented, Western Front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theatreOfWarDocumented Context triple: [Canadian War Memorials Fund, theatreOfWarDocumented, Western Front]
-
A.
theaterOfWar
Indicates that a specified location or region is the primary area where a particular conflict, war, or military operation takes place.
-
B.
militaryTheater
chosen
Indicates that an entity is a geographic or operational area where military operations or campaigns are conducted.
-
C.
theatreOfWorldWarIIService
Indicates the geographic region or operational area in which an entity participated in military service during World War II.
-
D.
sharesWorldWarTheater
Indicates that two military operations or events took place in the same theater of operations during a World War.
-
E.
warTheaterContext
Indicates the broader war or military campaign within which a specific battle, operation, or conflict event takes place.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:33 p.m.