Triple
T32028719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Torrey Canyon |
E817889
|
entity |
| Predicate | routeAtTimeOfAccident |
P173794
|
FINISHED |
| Object | Persian Gulf to Milford Haven |
—
|
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: Persian Gulf to Milford Haven | Statement: [SS Torrey Canyon, routeAtTimeOfAccident, Persian Gulf to Milford Haven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeAtTimeOfAccident Context triple: [SS Torrey Canyon, routeAtTimeOfAccident, Persian Gulf to Milford Haven]
-
A.
siteOfAccident
Indicates the location where an accident occurred.
-
B.
flagAtTimeOfAccident
Indicates that a particular flag or status was in effect at the specific time when the accident occurred.
-
C.
intendedDestinationAtAccident
Indicates that a location was the destination an entity was heading toward at the time an accident occurred.
-
D.
cargoAtTimeOfAccident
Indicates that a specified cargo was present or being carried at the moment an accident occurred.
-
E.
accidentOccurredDuring
Indicates that an accident took place within the time span or context of a specified event, activity, or condition.
- F. None of above. chosen
Provenance (4 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:17 a.m.