Triple
T24959149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ship That Would Not Die |
E624555
|
entity |
| Predicate | associatedShipClass |
P3141
|
FINISHED |
| Object | Allen M. Sumner-class destroyer |
—
|
NE NERFINISHED |
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: Allen M. Sumner-class destroyer | Statement: [The Ship That Would Not Die, associatedShipClass, Allen M. Sumner-class destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedShipClass Context triple: [The Ship That Would Not Die, associatedShipClass, Allen M. Sumner-class destroyer]
-
A.
shipClass
chosen
Indicates the classification or type category to which a particular ship belongs.
-
B.
usedOnShipClass
Indicates that something (such as equipment, technology, or a system) is employed or installed on a particular class of ship.
-
C.
hasShipInClass
Indicates that an entity possesses or includes at least one ship that belongs to a specified ship class.
-
D.
hasStarshipClassDepicted
Indicates that an entity includes or shows a depiction of a particular starship class.
-
E.
classOnShip
Indicates that an entity holds a particular class or status aboard a ship.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 18, 2026, 5:58 a.m.