Triple
T9296136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combined Forces Command |
E223642
|
entity |
| Predicate | commandStructureType |
P84958
|
FINISHED |
| Object | binational combined 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: binational combined command | Statement: [Combined Forces Command, commandStructureType, binational combined command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandStructureType Context triple: [Combined Forces Command, commandStructureType, binational combined command]
-
A.
commandStructureUnion
chosen
Indicates a relationship where multiple command structures are combined or unified into a single coordinated command framework.
-
B.
commandType
Indicates the specific kind or category of command being issued or executed in the relationship.
-
C.
hasCommandStructure
Indicates that one entity possesses an organized hierarchy of authority or control that governs another entity or set of entities.
-
D.
commandSyntax
Indicates the specific structure or format in which a command must be written or expressed.
-
E.
typeOfCommand
Indicates that one entity is a specific kind or category of command in relation to 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089c9c588190967404c9eb938dfb |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.