Triple
T38226281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Speicher |
E1012154
|
entity |
| Predicate | wasOnMission |
P105991
|
FINISHED |
| Object | first night of Operation Desert Storm |
—
|
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: first night of Operation Desert Storm | Statement: [Scott Speicher, wasOnMission, first night of Operation Desert Storm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOnMission Context triple: [Scott Speicher, wasOnMission, first night of Operation Desert Storm]
-
A.
operatedOnMission
Indicates that an agent carried out or participated in the execution of a specific mission.
-
B.
carriedOutMissionIn
Indicates that an entity performed or executed a specific mission in a particular context or location.
-
C.
hadMission
chosen
Indicates that an entity (such as a person, organization, or vehicle) was assigned or carried out a specific mission or operation.
-
D.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
E.
hasMissionTo
Indicates that an entity is assigned or dedicated to carrying out a specific mission, task, or purpose related to another entity or objective.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.