Triple
T28865216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filey Coble Landing |
E728978
|
entity |
| Predicate | hasAssociatedVesselType |
P11978
|
FINISHED |
| Object | coble |
—
|
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: coble | Statement: [Filey Coble Landing, hasAssociatedVesselType, coble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedVesselType Context triple: [Filey Coble Landing, hasAssociatedVesselType, coble]
-
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.
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.
-
C.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
D.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
E.
usesVesselsOperatedBy
Indicates that one entity makes use of vessels that are operated or controlled by 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 6:48 a.m.