Triple
T17071409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCI BMX Supercross World Cup |
E414229
|
entity |
| Predicate | trackFeatures |
P115884
|
FINISHED |
| Object | start hill |
—
|
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: start hill | Statement: [UCI BMX Supercross World Cup, trackFeatures, start hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackFeatures Context triple: [UCI BMX Supercross World Cup, trackFeatures, start hill]
-
A.
tracks
Indicates that one entity monitors, follows, or keeps a record of another entity’s state, behavior, or progress over time.
-
B.
hasTrackFeatures
chosen
Indicates that something possesses or is associated with specific track-related characteristics or attributes.
-
C.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
D.
trackDescription
Indicates the descriptive information or summary text associated with a specific track (such as a song, audio piece, or recorded segment).
-
E.
trackType
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc0982c8190916f9905ddb5e575 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.