Triple
T2202193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German heavy cruiser Prinz Eugen |
E50514
|
entity |
| Predicate | primaryWartimeRole |
P9463
|
FINISHED |
| Object | surface raider and fleet escort |
—
|
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: surface raider and fleet escort | Statement: [German heavy cruiser Prinz Eugen, primaryWartimeRole, surface raider and fleet escort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWartimeRole Context triple: [German heavy cruiser Prinz Eugen, primaryWartimeRole, surface raider and fleet escort]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
peacetimeRole
Indicates the role, function, or duties an entity holds during periods of peace rather than during wartime or conflict.
-
C.
worldWarIIRole
Indicates the specific role, position, or function an entity had in relation to World War II.
-
D.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
E.
preWorldWarIIRole
Indicates the role, position, or function an entity held or performed prior to the onset of World War II.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa1b41c8190b0f7467d0dcdfbcd |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.