Triple
T12940867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney to Hobart Yacht Race |
E309631
|
entity |
| Predicate | hasFinishLine |
P38695
|
FINISHED |
| Object | off Hobart on the River Derwent |
—
|
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: off Hobart on the River Derwent | Statement: [Sydney to Hobart Yacht Race, hasFinishLine, off Hobart on the River Derwent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinishLine Context triple: [Sydney to Hobart Yacht Race, hasFinishLine, off Hobart on the River Derwent]
-
A.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
B.
hasSprintFinish
Indicates that an event, activity, or process concludes with a short, intense final effort or burst of speed.
-
C.
hasStartFinishStraight
Indicates that something includes a straight segment that serves as both the starting and finishing section of a course or track.
-
D.
hasFinalAssemblyLine
Indicates that one entity serves as the final assembly line where another entity’s components or subassemblies are brought together and completed.
-
E.
hasEnd
chosen
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.