Triple
T21836966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M923 |
E539143
|
entity |
| Predicate | hasNATOStockNumber |
P6062
|
FINISHED |
| Object | 2320-01-206-4087 |
—
|
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: 2320-01-206-4087 | Statement: [M923, hasNATOStockNumber, 2320-01-206-4087]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNATOStockNumber Context triple: [M923, hasNATOStockNumber, 2320-01-206-4087]
-
A.
hasNATOCompatibleSystems
Indicates that an entity possesses systems or equipment that are compatible with NATO standards and can interoperate with NATO forces.
-
B.
NATOStandard
Indicates that something conforms to, is defined by, or is governed by standards established by NATO.
-
C.
NATOcode
chosen
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
D.
hasPartNumber
Indicates that one entity is assigned or associated with a specific part number used to identify it within a catalog, system, or inventory.
-
E.
hasNATOContext
Indicates that something is related to, influenced by, or situated within the context of NATO, its activities, policies, or structures.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a890208190a902184e60194e1c |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.