Triple
T28155263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OUBC |
E714724
|
entity |
| Predicate | boatRaceCourseRiver |
P85322
|
FINISHED |
| Object | River Thames |
—
|
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: River Thames | Statement: [OUBC, boatRaceCourseRiver, River Thames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatRaceCourseRiver Context triple: [OUBC, boatRaceCourseRiver, River Thames]
-
A.
boatRaceVenue
chosen
Indicates the location or venue where a boat race takes place.
-
B.
boatRaceRole
Indicates the specific role or function an entity has within the context of a boat race (e.g., participant, organizer, official).
-
C.
waterbodyOnCourse
Indicates that a waterbody lies along, intersects, or is situated on the path of a particular course, such as a river or stream.
-
D.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
E.
plannedOnRiver
Indicates that something is intended or designed to be located, constructed, or carried out on or along a river.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f641e667f88190928bd3315a0dc485 |
completed | May 2, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:02 p.m.