Triple
T21135805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Forces School of Communications and Electronics |
E520811
|
entity |
| Predicate | hasTrainingDomain |
P24513
|
FINISHED |
| Object | communications |
—
|
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: communications | Statement: [Canadian Forces School of Communications and Electronics, hasTrainingDomain, communications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingDomain Context triple: [Canadian Forces School of Communications and Electronics, hasTrainingDomain, communications]
-
A.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
B.
hasTrained
Indicates that one entity has provided training or instruction to another entity.
-
C.
hasTrainingType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of training.
-
D.
hasTrainingRole
Indicates that an entity holds or is assigned a specific role within a training or instructional context.
-
E.
hasTrainingTrack
Indicates that an entity is associated with or assigned to a specific training track or program.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235aae588190bf9f7b40553bfa0e |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:57 p.m.