Triple
T17617953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Chunuk Bair |
E429132
|
entity |
| Predicate | campaignGoalContext |
P32833
|
FINISHED |
| Object | secure Dardanelles for Allied naval forces |
—
|
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: secure Dardanelles for Allied naval forces | Statement: [Battle of Chunuk Bair, campaignGoalContext, secure Dardanelles for Allied naval forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignGoalContext Context triple: [Battle of Chunuk Bair, campaignGoalContext, secure Dardanelles for Allied naval forces]
-
A.
campaignObjectiveContext
chosen
Indicates the specific situational or strategic context in which a campaign’s objective is defined or pursued.
-
B.
aimOfCampaign
Indicates that a campaign is directed toward achieving a particular goal or objective.
-
C.
campaignObjectiveSpanish
Indicates the specific goal or purpose of a campaign as expressed in the Spanish language.
-
D.
campaignObjectivePersian
Indicates the specific goal or intended outcome of a campaign, expressed in the Persian language.
-
E.
campaignDirected
Indicates that a campaign is intentionally targeted or directed toward a specific entity or audience.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d33a2b081908deecee773c333af |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.