Triple
T27091191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Division of the Missouri |
E686171
|
entity |
| Predicate | hasCommandArea |
P197876
|
FINISHED |
| Object | Great Plains region |
—
|
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: Great Plains region | Statement: [Military Division of the Missouri, hasCommandArea, Great Plains region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommandArea Context triple: [Military Division of the Missouri, hasCommandArea, Great Plains region]
-
A.
hasCommand
Indicates that one entity possesses, controls, or is associated with a specific command or directive applied to another entity or process.
-
B.
hasCommandSystem
Indicates that one entity possesses, uses, or is associated with a particular command or control system.
-
C.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
D.
hasCommandFacilities
Indicates that an entity possesses locations, infrastructure, or resources used for command, control, or leadership functions.
-
E.
hasHigherCommand
Indicates that one entity holds a superior or higher-level command authority over another entity.
- F. None of above. chosen
Provenance (4 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
| PDg | Predicate description generation | batch_69feb5e50a7481908d6bff55bd85e06d |
completed | May 9, 2026, 4:19 a.m. |
Created at: April 27, 2026, 8:40 a.m.