Triple
T10904297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brighton Racecourse |
E257526
|
entity |
| Predicate | hasFinishType |
P65191
|
FINISHED |
| Object | uphill finish |
—
|
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: uphill finish | Statement: [Brighton Racecourse, hasFinishType, uphill finish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinishType Context triple: [Brighton Racecourse, hasFinishType, uphill finish]
-
A.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
B.
finishType
chosen
Indicates the manner or outcome by which an action, process, or event is completed.
-
C.
hasSprintFinish
Indicates that an event, activity, or process concludes with a short, intense final effort or burst of speed.
-
D.
hasFrameFinish
Indicates that an entity’s frame possesses a specific surface treatment or finish.
-
E.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d761a5dffc8190927b0928978646a4 |
completed | April 9, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.