Triple
T27780417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert "Bobby" Shatford |
E699320
|
entity |
| Predicate | vesselServedOn |
P53198
|
FINISHED |
| Object | Andrea Gail |
—
|
NE NERFINISHED |
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: Andrea Gail | Statement: [Robert "Bobby" Shatford, vesselServedOn, Andrea Gail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vesselServedOn Context triple: [Robert "Bobby" Shatford, vesselServedOn, Andrea Gail]
-
A.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
B.
vesselService
Indicates a service relationship in which one entity provides, operates, or maintains a vessel (such as a ship or boat) for another entity.
-
C.
namedVesselOf
Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to another entity.
-
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.
servedShip
chosen
Indicates that one entity performed service or duty aboard, or in direct support of, a particular ship.
- 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_69f637cd6cb88190890704547d681fb2 |
completed | May 2, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:09 p.m.