Triple
T32084030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 17th Canadian Infantry Brigade |
E819384
|
entity |
| Predicate | hasPrimaryArm |
P21872
|
FINISHED |
| Object | small arms |
—
|
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: small arms | Statement: [17th Canadian Infantry Brigade, hasPrimaryArm, small arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryArm Context triple: [17th Canadian Infantry Brigade, hasPrimaryArm, small arms]
-
A.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
B.
hasPrimarySystem
Indicates that an entity is associated with or operates under a main or principal system among potentially multiple systems.
-
C.
hasArm
chosen
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
-
D.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for another entity.
-
E.
hasPrimaryAbility
Indicates that an entity possesses a main or most important ability that characterizes its primary function or role.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00ac5654a0819090701f61a5802d64 |
completed | May 10, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_6a00ab94b5e881909e15d1342e5f43be |
completed | May 10, 2026, 4 p.m. |
Created at: May 1, 2026, 12:24 a.m.