Triple
T33430786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS Nymphe |
E856123
|
entity |
| Predicate | roleDuringSecondSchleswigWar |
P176601
|
FINISHED |
| Object | Prussian naval operations against Denmark |
—
|
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: Prussian naval operations against Denmark | Statement: [SMS Nymphe, roleDuringSecondSchleswigWar, Prussian naval operations against Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleDuringSecondSchleswigWar Context triple: [SMS Nymphe, roleDuringSecondSchleswigWar, Prussian naval operations against Denmark]
-
A.
allyDuringAustroPrussianWar
Indicates that one entity was an ally of another during the Austro-Prussian War.
-
B.
roleInGermanUnification
Indicates the specific function, contribution, or involvement an entity had in the historical process of German unification.
-
C.
roleInBattleOfGravelotte
Indicates the specific role or participation an entity had in the Battle of Gravelotte.
-
D.
monarchOfPrussiaDuringWar
Indicates the person who held the position of monarch of Prussia during a specified war.
-
E.
sideAtBattleOfLeipzig
Indicates that an entity participated as a belligerent side in the Battle of Leipzig.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52a6d40819084472f6072c91e9f |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:36 a.m.