Triple
T29866248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Command Authority |
E758464
|
entity |
| Predicate | issuesOrdersTo |
P157749
|
FINISHED |
| Object | combatant commands |
—
|
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: combatant commands | Statement: [National Command Authority, issuesOrdersTo, combatant commands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuesOrdersTo Context triple: [National Command Authority, issuesOrdersTo, combatant commands]
-
A.
isOrderedTo
chosen
Indicates that one entity has been formally directed or commanded to perform an action or fulfill a duty by another authority.
-
B.
isOrderIn
Indicates that one entity is contained within or belongs to a specified order or sequence of entities.
-
C.
orderRegardedAs
Indicates that one order is considered or treated as equivalent to, or in the same category as, another order within a given context or system.
-
D.
issuePrice
Indicates the price at which a financial instrument (such as a security or bond) is originally issued to investors.
-
E.
orderWithin
Indicates that one entity is positioned or ranked before or after another entity within a defined sequence or ordering.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 5:51 p.m.