Triple
T7864276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Women’s Boat Race |
E182576
|
entity |
| Predicate | movedToTideway |
P79439
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [The Women’s Boat Race, movedToTideway, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedToTideway Context triple: [The Women’s Boat Race, movedToTideway, 2015]
-
A.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
B.
waterwayTypeCrossed
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
-
C.
acrossWaterFrom
Indicates that two entities are located on opposite sides of a body of water, separated by that water.
-
D.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
E.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb36c0eaa48190a0df4c37c726546e |
completed | March 31, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:54 p.m.