Triple
T31177429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Canadian Infantry Brigade |
E794788
|
entity |
| Predicate | branchDuringWWI |
P38552
|
FINISHED |
| Object | Canadian Expeditionary Force |
—
|
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: Canadian Expeditionary Force | Statement: [1st Canadian Infantry Brigade, branchDuringWWI, Canadian Expeditionary Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchDuringWWI Context triple: [1st Canadian Infantry Brigade, branchDuringWWI, Canadian Expeditionary Force]
-
A.
serviceBranchDuringWorldWarI
chosen
Indicates that an entity served in a specified military branch during World War I.
-
B.
positionOnWorldWarI
Indicates a person’s or group’s stance, opinion, or policy regarding World War I.
-
C.
controlledByDuringWWI
Indicates that one entity exercised political or military control over another entity specifically during the period of World War I.
-
D.
legalStatusDuringWWI
Indicates the legal condition or classification an entity held specifically during World War I (e.g., enemy alien, neutral, ally, civilian, combatant).
-
E.
roleInWorldWarI
Indicates the specific function, position, or involvement an entity had during World War I.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:08 p.m.