Triple
T28387028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Headquarters, U.S. Army (in concept) |
E719044
|
entity |
| Predicate | commandFocus |
P86548
|
FINISHED |
| Object | land combat operations |
—
|
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: land combat operations | Statement: [General Headquarters, U.S. Army (in concept), commandFocus, land combat operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandFocus Context triple: [General Headquarters, U.S. Army (in concept), commandFocus, land combat operations]
-
A.
importFocus
Indicates that attention, priority, or emphasis is being brought into or concentrated on a particular entity or aspect.
-
B.
canonicalFocus
Indicates that one entity is the primary or most representative focus or point of attention in relation to another entity.
-
C.
focusOf
chosen
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
D.
instrumentFocus
Indicates that the relationship or action specifically emphasizes or centers on the instrument used to perform it.
-
E.
focusShift
Indicates a change in attention or emphasis from one entity or topic to another.
- 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_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 1:10 a.m.