Triple
T1649765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Member of the Order of Canada |
E35663
|
entity |
| Predicate | isNonMilitary |
P2334
|
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: [Member of the Order of Canada, isNonMilitary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonMilitary Context triple: [Member of the Order of Canada, isNonMilitary, true]
-
A.
isCivilian
chosen
Indicates that an entity is a non-military, non-combatant individual in the context of a given situation or system.
-
B.
isCivilianOffice
Indicates that an office or position is non-military and belongs to the civilian sphere of authority or administration.
-
C.
militaryStatus
Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
-
D.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
E.
hasMilitaryAssociation
Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaa0fbe984819084f8daee81ca9b67 |
completed | March 6, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69a907ce4dd881909168a1e99505d4ec |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.