Triple
T8049491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canadian Electrical and Mechanical Engineers |
E187637
|
entity |
| Predicate | equipmentDomain |
P15250
|
FINISHED |
| Object | armoured vehicles |
—
|
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: armoured vehicles | Statement: [Royal Canadian Electrical and Mechanical Engineers, equipmentDomain, armoured vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentDomain Context triple: [Royal Canadian Electrical and Mechanical Engineers, equipmentDomain, armoured vehicles]
-
A.
typeOfEquipmentManaged
chosen
Indicates the specific kind or category of equipment that an entity is responsible for managing.
-
B.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
C.
hardwareUsedBy
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
-
D.
relatedDevice
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
-
E.
includesDevices
Indicates that one entity contains, encompasses, or has as part of it one or more devices.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f7826288190b2f292a7d34fcd80 |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:24 p.m.