Triple
T25435653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlemagne |
E637364
|
entity |
| Predicate | navalCampaignParticipation |
P158511
|
FINISHED |
| Object | Crimean War Baltic operations |
—
|
NE NERFINISHED |
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: Crimean War Baltic operations | Statement: [Charlemagne, navalCampaignParticipation, Crimean War Baltic operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalCampaignParticipation Context triple: [Charlemagne, navalCampaignParticipation, Crimean War Baltic operations]
-
A.
warParticipatedIn
Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
-
B.
battlesWith
Indicates that two entities are engaged in active conflict, combat, or struggle against each other.
-
C.
battleshipInvolved
Indicates that a battleship participates as an active party in a specific event, operation, or engagement.
-
D.
battleParticipated
Indicates that an entity took part in a specific battle as a combatant or participant.
-
E.
militaryCampaignOf
Indicates a relationship where a specific military campaign is conducted by, initiated by, or belongs to a particular military force, state, or commander.
- F. None of above. chosen
Provenance (4 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6deaf288190aed44d1533fb95d5 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:59 p.m.