Triple
T33136384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaiserliche Werft Danzig |
E848016
|
entity |
| Predicate | navalBranchServed |
P91149
|
FINISHED |
| Object | Kaiserliche Marine |
—
|
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: Kaiserliche Marine | Statement: [Kaiserliche Werft Danzig, navalBranchServed, Kaiserliche Marine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalBranchServed Context triple: [Kaiserliche Werft Danzig, navalBranchServed, Kaiserliche Marine]
-
A.
navalWarfareBranch
Indicates that one entity is a branch or component of naval warfare to which the other entity belongs or with which it is associated.
-
B.
militaryUnitTypeServed
Indicates that an entity served in, or was a member of, a specific type of military unit.
-
C.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
-
D.
militaryBranchAssociatedWith
chosen
Indicates a relationship where an entity is connected to, or operates as part of, a specific branch of a military organization.
-
E.
hasNavalRole
Indicates that an entity holds or is assigned a role, function, or duty within a naval or maritime context.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:27 a.m.