Triple
T34591120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West German Army |
E888182
|
entity |
| Predicate | equipmentStandardizationWith |
P121725
|
FINISHED |
| Object | other NATO armies |
—
|
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: other NATO armies | Statement: [West German Army, equipmentStandardizationWith, other NATO armies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentStandardizationWith Context triple: [West German Army, equipmentStandardizationWith, other NATO armies]
-
A.
componentStandardization
chosen
Indicates that one entity is standardized, normalized, or made uniform according to the specifications, rules, or format defined by another entity.
-
B.
equipmentProvider
Indicates that one entity supplies or makes available equipment for use by another entity.
-
C.
standardEquipmentCategory
Indicates that an item belongs to a designated standard equipment category or classification.
-
D.
standardsUsedIn
Indicates that certain standards are applied, referenced, or followed within a particular context, process, or entity.
-
E.
equipmentRegulations
Indicates that there are rules or standards governing the use, maintenance, or management of specified 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.