Triple
T37092280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Ulysses |
E918454
|
entity |
| Predicate | hasFictionalShipName |
P69373
|
FINISHED |
| Object | HMS Ulysses |
—
|
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 Ulysses | Statement: [HMS Ulysses, hasFictionalShipName, HMS Ulysses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalShipName Context triple: [HMS Ulysses, hasFictionalShipName, HMS Ulysses]
-
A.
fictionalShip
chosen
Indicates that one entity is a ship that exists only in fiction or narrative works, rather than in reality.
-
B.
namesakeShip
Indicates that one entity is a ship that is named after, or serves as the namesake of, another entity.
-
C.
isCapitalShip
Indicates that the subject vessel is classified as a capital ship, i.e., a primary, large, and heavily armed warship within a fleet.
-
D.
shipName
Indicates the name assigned to a specific ship in the relationship.
-
E.
craftName
Indicates that an entity is identified by the specific name of a craft, vehicle, or vessel.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00474f08908190bc8ae3b320ec887b |
completed | May 10, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_6a0045dc3bd48190a9e0520f3ef3f067 |
completed | May 10, 2026, 8:46 a.m. |
Created at: May 3, 2026, 4:14 p.m.