Triple
T4385461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander, U.S. Strategic Command |
E99229
|
entity |
| Predicate | establishedAsPositionIn |
P28028
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Commander, U.S. Strategic Command, establishedAsPositionIn, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsPositionIn Context triple: [Commander, U.S. Strategic Command, establishedAsPositionIn, 1992]
-
A.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
B.
positionEstablishedIn
chosen
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
C.
establishedTo
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
-
D.
positionEstablishedFor
Indicates that a specific role or job position has been formally created or set up for a particular entity or purpose.
-
E.
initiallyPositionedAs
Indicates that one entity’s starting or original position is specified relative to another entity or reference frame.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35264e44c81908dd0e0a81f1353bb |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.