Triple
T24380195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Pretoria |
E614585
|
entity |
| Predicate | navalHistoryTopic |
P96804
|
FINISHED |
| Object | German merchant marine in World War II |
—
|
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: German merchant marine in World War II | Statement: [SS Pretoria, navalHistoryTopic, German merchant marine in World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalHistoryTopic Context triple: [SS Pretoria, navalHistoryTopic, German merchant marine in World War II]
-
A.
navalHistory
chosen
Indicates a relationship where an entity is associated with the study, record, or events of naval or maritime military history.
-
B.
navalEra
Indicates the historical period or era in which a naval-related event, activity, or condition takes place.
-
C.
militaryHistoryTopic
Indicates that there exists a relationship where the subject is a topic, theme, or subject matter specifically concerned with military history.
-
D.
shipHistoricalRole
Indicates the historical function or significance a ship had, such as its role in events, conflicts, or periods of service.
-
E.
navalTechnologySignificance
Indicates the importance or impact that a particular naval technology has within a given historical, strategic, or operational 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293db31c481908484ab28921cd5fd |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.