Triple
T24063398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary Regiment (Tank) |
E596017
|
entity |
| Predicate | branchSpeciality |
P89408
|
FINISHED |
| Object | armour |
—
|
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: armour | Statement: [Calgary Regiment (Tank), branchSpeciality, armour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchSpeciality Context triple: [Calgary Regiment (Tank), branchSpeciality, armour]
-
A.
subjectSpecialization
Indicates that one subject focuses on, or has expertise in, a particular field, topic, or area of knowledge.
-
B.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
C.
branchSpecialization
chosen
Indicates that one branch or subdivision is specialized or focused in a particular area, function, or domain relative to others.
-
D.
openingSpecialty
Indicates the specific area of focus, expertise, or type associated with an opening (such as a job, position, or opportunity).
-
E.
parentOrganizationSpecialty
Indicates that a specialty or sub-discipline is associated with, or falls under the scope of, a broader parent organization.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da5825548190b94cb6e708617a7d |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:39 p.m.