Triple
T28387011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Headquarters, U.S. Army (in concept) |
E719044
|
entity |
| Predicate | wouldCommand |
P165153
|
FINISHED |
| Object | field armies |
—
|
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: field armies | Statement: [General Headquarters, U.S. Army (in concept), wouldCommand, field armies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wouldCommand Context triple: [General Headquarters, U.S. Army (in concept), wouldCommand, field armies]
-
A.
couldCommand
chosen
Indicates that one entity had the authority, power, or position to issue orders or directives to another entity.
-
B.
coCommandedWith
Indicates that two or more entities shared command authority together over the same unit, operation, or context during a given period.
-
C.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
D.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
E.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 1:10 a.m.