Triple
T26300814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordnance Corps |
E661551
|
entity |
| Predicate | hasDoctrineArea |
P162327
|
FINISHED |
| Object | explosive ordnance operations |
—
|
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: explosive ordnance operations | Statement: [Ordnance Corps, hasDoctrineArea, explosive ordnance operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoctrineArea Context triple: [Ordnance Corps, hasDoctrineArea, explosive ordnance operations]
-
A.
hasDoctrineArea
chosen
Indicates that one entity is associated with, or pertains to, a particular doctrinal area or field of doctrine.
-
B.
isPartOfDoctrineArea
Indicates that one concept, topic, or element belongs to or falls within the scope of a particular doctrinal area or field of doctrine.
-
C.
containsDoctrine
Indicates that one entity includes, embodies, or incorporates the doctrine, principles, or teachings represented by another entity.
-
D.
usesDoctrine
Indicates that one entity applies, follows, or relies on a particular doctrine in its actions or reasoning.
-
E.
acceptsDoctrine
Indicates that one entity acknowledges, adopts, or agrees to follow the doctrine put forward by another entity.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 26, 2026, 10:15 p.m.