Triple
T7169462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putney Embankment |
E167154
|
entity |
| Predicate | boatRaceRole |
P74512
|
FINISHED |
| Object | starting area for the Boat Race |
—
|
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: starting area for the Boat Race | Statement: [Putney Embankment, boatRaceRole, starting area for the Boat Race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatRaceRole Context triple: [Putney Embankment, boatRaceRole, starting area for the Boat Race]
-
A.
sixthBoat
Indicates that an entity is the sixth boat in an ordered sequence or arrangement of boats.
-
B.
secondBoat
Indicates that one entity is the second boat in a sequence or relative ordering with respect to another boat.
-
C.
craftType
Indicates the specific kind or category of craft or vessel associated with an entity.
-
D.
sailingDiscipline
Indicates a specific category or type of sailing activity or competition in which an entity participates or is involved.
-
E.
sailingSeries
Indicates a relationship where multiple sailing events or races are grouped together as part of the same organized series or competition.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85c606081909f76d76fc5b90bc8 |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1ce5f048190808c378a980f7bb6 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e24af9ac8190b24eee206ba8be36 |
completed | March 27, 2026, 8:02 p.m. |
Created at: March 27, 2026, 2:48 p.m.