Triple
T7164398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socialist Party of Canada |
E167029
|
entity |
| Predicate | stanceOnWorldWarI |
P10699
|
FINISHED |
| Object | generally opposed to imperialist war |
—
|
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: generally opposed to imperialist war | Statement: [Socialist Party of Canada, stanceOnWorldWarI, generally opposed to imperialist war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceOnWorldWarI Context triple: [Socialist Party of Canada, stanceOnWorldWarI, generally opposed to imperialist war]
-
A.
roleInWorldWarI
Indicates the specific function, position, or involvement an entity had during World War I.
-
B.
positionOnWorldWarI
chosen
Indicates a person’s or group’s stance, opinion, or policy regarding World War I.
-
C.
worldWarIIService
Indicates that an entity served in some capacity during World War II.
-
D.
worldWar
Indicates a large-scale armed conflict involving multiple nations across different regions of the world, typically encompassing numerous battles, alliances, and theaters of war.
-
E.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e83168a08190937ff46797d94f3e |
completed | March 27, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.