Triple
T11184559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Big Hole |
E264627
|
entity |
| Predicate | hasCampaignObjective |
P50135
|
FINISHED |
| Object | U.S. attempt to halt Nez Perce flight |
—
|
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: U.S. attempt to halt Nez Perce flight | Statement: [Battle of the Big Hole, hasCampaignObjective, U.S. attempt to halt Nez Perce flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampaignObjective Context triple: [Battle of the Big Hole, hasCampaignObjective, U.S. attempt to halt Nez Perce flight]
-
A.
campaignObjectiveContext
Indicates the specific situational or strategic context in which a campaign’s objective is defined or pursued.
-
B.
campaignObjectivePersian
Indicates the specific goal or intended outcome of a campaign, expressed in the Persian language.
-
C.
hasMarketingCampaign
Indicates that an entity is associated with or utilizes a specific marketing campaign.
-
D.
hasMarketingTarget
Indicates that an entity is aimed at or intended to appeal to a specific marketing audience or segment.
-
E.
aimOfCampaign
chosen
Indicates that a campaign is directed toward achieving a particular goal 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8a9c5e081908c85b41a268428fb |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.