Triple
T22652169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R 104 |
E559121
|
entity |
| Predicate | vesselTypeIdentified |
P11978
|
FINISHED |
| Object | oceanographic research vessel |
—
|
LITERAL 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: oceanographic research vessel | Statement: [R 104, vesselTypeIdentified, oceanographic research vessel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vesselTypeIdentified Context triple: [R 104, vesselTypeIdentified, oceanographic research vessel]
-
A.
hasVesselType
chosen
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
B.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
C.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
D.
hasVessel
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
-
E.
namedVesselOf
Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to another entity.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703d7d648190aafe275cd04c47cf |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:06 p.m.