Triple
T23854768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Men in a Boat |
E592272
|
entity |
| Predicate | riverTravelRoute |
P14751
|
FINISHED |
| Object | Kingston upon Thames to Oxford |
—
|
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: Kingston upon Thames to Oxford | Statement: [Three Men in a Boat, riverTravelRoute, Kingston upon Thames to Oxford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverTravelRoute Context triple: [Three Men in a Boat, riverTravelRoute, Kingston upon Thames to Oxford]
-
A.
riverExplored
Indicates that an entity has been explored or surveyed along the course of a river.
-
B.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
C.
hasRaftingDifficulty
Indicates that an entity is associated with a specific level of rafting difficulty.
-
D.
isOnlyNavigableRiverOf
Indicates that one river is the sole river that can be navigated within a specified area or context.
-
E.
waterTransport
chosen
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98a60b081908dbdc359f51e67fa |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.