Triple
T27780407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William "Billy" Tyne Jr. |
E699319
|
entity |
| Predicate | crewCommanded |
P147261
|
FINISHED |
| Object | crew of the Andrea Gail |
—
|
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: crew of the Andrea Gail | Statement: [William "Billy" Tyne Jr., crewCommanded, crew of the Andrea Gail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewCommanded Context triple: [William "Billy" Tyne Jr., crewCommanded, crew of the Andrea Gail]
-
A.
fleetCommander
Indicates that one entity serves as the commanding officer or overall leader in charge of the operations and decisions of a fleet associated with another entity.
-
B.
commandCrew
chosen
Indicates that one entity holds command authority over the crew associated with another entity.
-
C.
commanderOnBoard
Indicates that a specific individual holds the role of commanding officer on a particular vehicle, vessel, or craft during its operation.
-
D.
crewSystem
Indicates a relationship where a system is specifically designed for, assigned to, or operated by a particular crew.
-
E.
commandedFromShip
Indicates that an entity exercised command or control over something while located on or operating from a 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.