Triple
T36390802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Native River |
E896320
|
entity |
| Predicate | raceRecordCategory |
P49218
|
FINISHED |
| Object | Grade 1 steeplechaser |
—
|
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: Grade 1 steeplechaser | Statement: [Native River, raceRecordCategory, Grade 1 steeplechaser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceRecordCategory Context triple: [Native River, raceRecordCategory, Grade 1 steeplechaser]
-
A.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
-
B.
raceRecord
Indicates that there exists a recorded result or performance entry for an entity participating in a race or competitive event.
-
C.
recordSpeedCategory
Indicates the classification of an entity’s speed into a predefined category (e.g., slow, normal, fast) based on its recorded speed.
-
D.
raceTypeDetail
chosen
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
E.
F1LapRecordCategory
Indicates that an entity holds or pertains to a specific category of Formula 1 lap record (such as overall, qualifying, or race lap records).
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.