Triple
T30364320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Conway |
E772372
|
entity |
| Predicate | shipComponent |
P38891
|
FINISHED |
| Object | HMS Nile (as training ship hull) |
—
|
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 Nile (as training ship hull) | Statement: [HMS Conway, shipComponent, HMS Nile (as training ship hull)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipComponent Context triple: [HMS Conway, shipComponent, HMS Nile (as training ship hull)]
-
A.
componentShip
chosen
Indicates that one entity is a physical or logical component or part of another entity, such that the whole is composed of or depends on that component.
-
B.
shipMaterial
Indicates that one entity is the material or substance from which the ship entity is made or constructed.
-
C.
marineComponent
Indicates a relationship where something is a part, subsystem, or element of a marine or sea-related system, structure, or environment.
-
D.
shipDraft
Indicates the depth of a ship’s hull below the waterline, typically representing how deeply the vessel sits in the water.
-
E.
shipCompanion
Indicates that one entity serves as a companion or partner accompanying another entity on a ship or sea voyage.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6827ecae8819092c15bbb1529dbad |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:58 p.m.