Triple
T33088448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walther Schwieger |
E846706
|
entity |
| Predicate | submarineTypeCommanded |
P171713
|
FINISHED |
| Object | Type U 19-class submarine |
—
|
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: Type U 19-class submarine | Statement: [Walther Schwieger, submarineTypeCommanded, Type U 19-class submarine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: submarineTypeCommanded Context triple: [Walther Schwieger, submarineTypeCommanded, Type U 19-class submarine]
-
A.
submarineClassName
chosen
Indicates the specific class designation or type category to which a submarine belongs.
-
B.
submarineClassRole
Indicates the functional role or mission type assigned to a particular class of submarines within a naval context.
-
C.
submarineClassLeadShip
Indicates that one entity is the lead (first-built or first-commissioned) ship of a particular submarine class represented by the other entity.
-
D.
primarySubmarineClassSupported
Indicates that an entity is designed to support, service, or operate primarily with a specific class of submarines.
-
E.
submarine
Indicates that one entity is a submarine in relation to another entity or 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.