Triple
T17420786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HNLMS Piet Hein |
E423607
|
entity |
| Predicate | timeOfSinking |
P18834
|
FINISHED |
| Object | early stages of World War II in the Pacific |
—
|
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: early stages of World War II in the Pacific | Statement: [HNLMS Piet Hein, timeOfSinking, early stages of World War II in the Pacific]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfSinking Context triple: [HNLMS Piet Hein, timeOfSinking, early stages of World War II in the Pacific]
-
A.
dateOfSinking
Indicates the specific calendar date on which an entity (typically a vessel or structure) sank.
-
B.
missionAtTimeOfSinking
Indicates that a vessel was engaged in a specific mission or operational role at the time it sank.
-
C.
yearOfSinking
Indicates the specific calendar year in which an entity (typically a vessel or structure) sank.
-
D.
legalStatusAtTimeOfSinking
Indicates the legal status or condition that applied to an entity at the specific time it sank.
-
E.
sunkDuring
chosen
Indicates that one entity was sunk in the course of, or as a result of, the event or time period represented by another entity.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e442372954819085f332efc7067ae9 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.