Triple
T27780440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dale Murphy |
E699321
|
entity |
| Predicate | employedOnVesselType |
P114106
|
FINISHED |
| Object | commercial fishing 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: commercial fishing vessel | Statement: [Dale Murphy, employedOnVesselType, commercial fishing vessel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedOnVesselType Context triple: [Dale Murphy, employedOnVesselType, commercial fishing vessel]
-
A.
vesselTypeServedOn
chosen
Indicates the type of vessel on which an entity has served or performed duty.
-
B.
hasVesselType
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.
sponsoredVesselType
Indicates that one entity has provided sponsorship or financial backing specifically for a vessel of a given type.
-
E.
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.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 5:09 p.m.