Triple
T16741789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Army doctrine |
E406850
|
entity |
| Predicate | incorporatesConcept |
P531
|
FINISHED |
| Object | mission command |
—
|
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: mission command | Statement: [British Army doctrine, incorporatesConcept, mission command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporatesConcept Context triple: [British Army doctrine, incorporatesConcept, mission command]
-
A.
commonConcept
Indicates that two or more entities share the same underlying idea, notion, or conceptual meaning.
-
B.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
C.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
D.
refinedConcept
Indicates that one concept is a more precise, detailed, or specialized version of another concept.
-
E.
incorporatedAs
Indicates that an organization has been legally formed and registered under a specific corporate structure or name.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3f49808190b543d8da34031f3d |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.