Triple
T36834642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Argonaut |
E910236
|
entity |
| Predicate | previousShipWithSameName |
P200128
|
FINISHED |
| Object | HMS Argonaut (WWII cruiser) |
—
|
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: HMS Argonaut (WWII cruiser) | Statement: [HMS Argonaut, previousShipWithSameName, HMS Argonaut (WWII cruiser)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousShipWithSameName Context triple: [HMS Argonaut, previousShipWithSameName, HMS Argonaut (WWII cruiser)]
-
A.
previousShipClass
Indicates that one ship class directly precedes another in a sequence or lineage of ship classes.
-
B.
successorVesselNameReuse
chosen
Indicates that a later vessel reuses the name of an earlier vessel as its successor.
-
C.
lastShip
Indicates that one entity is the final or most recent ship associated with another entity in a given sequence, context, or process.
-
D.
renamedShipAs
Indicates that one entity changed the name of a ship to another specified name.
-
E.
secondShipRenamedAs
Indicates that a second ship has been given a new name, establishing a renaming relationship between its prior and current identities.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:13 p.m.