Triple
T38703451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lütjens-class destroyer |
E950199
|
entity |
| Predicate | notableShipPreservedAsMuseum |
P60408
|
FINISHED |
| Object | D185 Mölders |
E2281604
|
NE 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: D185 Mölders | Statement: [Lütjens-class destroyer, notableShipPreservedAsMuseum, D185 Mölders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableShipPreservedAsMuseum Context triple: [Lütjens-class destroyer, notableShipPreservedAsMuseum, D185 Mölders]
-
A.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
B.
hasMuseumShip
chosen
Indicates that one entity possesses or is associated with a museum ship, typically a preserved vessel displayed for public exhibition.
-
C.
becameMuseumShip
Indicates that a vessel or ship was converted from active service into a museum exhibit open to the public.
-
D.
notableVesselBuilt
Indicates that a particular vessel was constructed by or for the subject and is notable or significant in that context.
-
E.
hasMaritimeMuseum
Indicates that one entity possesses, hosts, or includes a maritime museum as part of its features or facilities.
- F. None of above.
Provenance (4 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a420e0889e4819098b40228702d3148 |
completed | June 29, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.