Triple
T28852333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordnance Stores Corps |
E728633
|
entity |
| Predicate | equipmentManaged |
P15250
|
FINISHED |
| Object | weapons |
—
|
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: weapons | Statement: [Ordnance Stores Corps, equipmentManaged, weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentManaged Context triple: [Ordnance Stores Corps, equipmentManaged, weapons]
-
A.
typeOfEquipmentManaged
chosen
Indicates the specific kind or category of equipment that an entity is responsible for managing.
-
B.
productTypeManaged
Indicates that an entity is responsible for overseeing, controlling, or administering a particular type of product.
-
C.
assetManagementFunction
Indicates the function or role responsible for overseeing, controlling, and optimizing the use and lifecycle of assets.
-
D.
equipmentProvider
Indicates that one entity supplies or makes available equipment for use by another entity.
-
E.
equipmentIssue
Indicates that there is a problem, malfunction, or defect affecting a piece of equipment.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f659d9ced481908ae528169fa6cd28 |
completed | May 2, 2026, 8:08 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:44 a.m.