Triple
T25393982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minatogawa Fishing Port |
E636239
|
entity |
| Predicate | hasVessels |
P11978
|
FINISHED |
| Object | coastal trawlers |
—
|
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: coastal trawlers | Statement: [Minatogawa Fishing Port, hasVessels, coastal trawlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVessels Context triple: [Minatogawa Fishing Port, hasVessels, coastal trawlers]
-
A.
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.
-
B.
hasVesselType
chosen
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
C.
usesVesselsOperatedBy
Indicates that one entity makes use of vessels that are operated or controlled by another entity.
-
D.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
E.
hasHistoricVesselsFrom
Indicates that an entity possesses or includes historic vessels that originate from a specified place or source.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:49 p.m.