Triple
T27916766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boat Race Company |
E706094
|
entity |
| Predicate | primaryEventLocation |
P147149
|
FINISHED |
| Object | Championship Course on the 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: Championship Course on the River Thames | Statement: [Boat Race Company, primaryEventLocation, Championship Course on the River Thames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEventLocation Context triple: [Boat Race Company, primaryEventLocation, Championship Course on the River Thames]
-
A.
locationOfEventOrganized
chosen
Indicates the place where a particular organized event is held or takes place.
-
B.
locationOfEventDescribed
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
C.
eventLocationDetail
Indicates the specific place or venue where an event occurs, often providing more granular location information than a general address or area.
-
D.
secondEventLocation
Indicates the location where the second event in a sequence takes place.
-
E.
sponsorLocation
Indicates that an entity acts as a sponsor for activities, events, or operations occurring at a specified location.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ffaa7bc45c8190b907db8579244a7b |
completed | May 9, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69ffa9f6c9a481908fbd4d18b311cbe2 |
completed | May 9, 2026, 9:41 p.m. |
Created at: April 27, 2026, 6:54 p.m.