Triple
T20758613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiddensee |
E510911
|
entity |
| Predicate | hasNavyPrefix |
P80388
|
FINISHED |
| Object | ex-Volksmarine |
—
|
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: ex-Volksmarine | Statement: [Hiddensee, hasNavyPrefix, ex-Volksmarine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavyPrefix Context triple: [Hiddensee, hasNavyPrefix, ex-Volksmarine]
-
A.
navyDesignationPrefix
chosen
Indicates the specific naval designation or prefix assigned to an entity, typically reflecting its role, type, or status within a navy.
-
B.
hasShipPrefix
Indicates that a ship is associated with or identified by a specific prefix in its name or designation.
-
C.
navy
Indicates that an entity serves as or is associated with a nation's naval military force.
-
D.
previousNavy
Indicates that one entity previously served in, belonged to, or was part of a navy before the current point in time.
-
E.
usedInNavy
Indicates that something is or was employed, operated, or otherwise utilized by a navy or naval forces.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2464fb08190b6b141ca12d9f3f4 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:35 p.m.