Triple
T33988327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IX-300 |
E871471
|
entity |
| Predicate | originatingShipClass |
P3141
|
FINISHED |
| Object | Admiral Hipper-class heavy cruiser |
E871470
|
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: Admiral Hipper-class heavy cruiser | Statement: [IX-300, originatingShipClass, Admiral Hipper-class heavy cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatingShipClass Context triple: [IX-300, originatingShipClass, Admiral Hipper-class heavy cruiser]
-
A.
shipClass
chosen
Indicates the classification or type category to which a particular ship belongs.
-
B.
originalShipType
Indicates the type or category of ship that an entity was originally classified or built as.
-
C.
shipClassDeveloped
Indicates that a particular ship class was developed or designed by a specified entity (such as a country, organization, or manufacturer).
-
D.
previousShipClass
Indicates that one ship class directly precedes another in a sequence or lineage of ship classes.
-
E.
originalNavyOfShip
Indicates the navy to which a ship originally belonged or was first commissioned, regardless of any later transfers or changes in ownership.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3692df83ac819093bb89144f4f9490 |
completed | June 20, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:50 a.m.