Triple
T28432205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canadian Army Cadets |
E715163
|
entity |
| Predicate | isNonCombatant |
P61973
|
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: [Royal Canadian Army Cadets, isNonCombatant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonCombatant Context triple: [Royal Canadian Army Cadets, isNonCombatant, true]
-
A.
combatOrNonCombat
chosen
Indicates whether an entity is involved in combat activities or is in a non-combat role or situation.
-
B.
isCivilian
Indicates that an entity is a non-military, non-combatant individual in the context of a given situation or system.
-
C.
nonCombatEquivalentOf
Indicates that one entity serves as the non-combat or peaceful counterpart of another entity that is oriented toward combat or warfare.
-
D.
isCombatUnit
Indicates that an entity functions as a unit specifically designated and equipped to engage in combat operations.
-
E.
isNonCombatDecoration
Indicates that an award or decoration is given for non-combat service or achievements rather than for participation in direct combat.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:40 a.m.