Triple
T23066217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTDL |
E575048
|
entity |
| Predicate | identifiesVesselType |
P11978
|
FINISHED |
| Object | 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: research vessel | Statement: [WTDL, identifiesVesselType, research vessel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesVesselType Context triple: [WTDL, identifiesVesselType, 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.
vesselRoleIdentified
Indicates that the specific functional role or purpose of a vessel within a context (e.g., a system, process, or operation) has been determined and recorded.
-
C.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
D.
IMOCategory
Indicates the classification of an entity according to the International Mathematical Olympiad (IMO) category it belongs to.
-
E.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f189a3e39481909cad356ad0bb3ee6 |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.