Triple
T2382044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Canadian Armoured Brigade |
E46330
|
entity |
| Predicate | primaryArm |
P6066
|
FINISHED |
| Object | tanks |
—
|
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: tanks | Statement: [2nd Canadian Armoured Brigade, primaryArm, tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryArm Context triple: [2nd Canadian Armoured Brigade, primaryArm, tanks]
-
A.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
B.
primaryArmament
chosen
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
C.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
D.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
-
E.
primaryForce
Indicates that one entity serves as the main or dominant force acting upon, influencing, or driving another entity or process.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7b98c988190abdb4fe51bf65bde |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.