Triple
T11370377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German cruiser Lützow |
E269323
|
entity |
| Predicate | reclassification |
P22031
|
FINISHED |
| Object | re-rated as heavy cruiser by Germany in 1940 |
—
|
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: re-rated as heavy cruiser by Germany in 1940 | Statement: [German cruiser Lützow, reclassification, re-rated as heavy cruiser by Germany in 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reclassification Context triple: [German cruiser Lützow, reclassification, re-rated as heavy cruiser by Germany in 1940]
-
A.
reclassifiedAs
chosen
Indicates that an entity’s classification or category has been changed from a previous one to a new one.
-
B.
reclassifiedBy
Indicates that an entity’s classification or category has been changed by a specific agent or authority.
-
C.
reclassificationYear
Indicates the year in which something was reassigned to a different category, status, or classification.
-
D.
classificationChange
Indicates a change in the category, type, or status under which an entity is classified.
-
E.
classificationMayChange
Indicates that the classification or category assigned to an entity is not fixed and can be updated or altered over time.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.