Triple
T18318807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Native Trail |
E438815
|
entity |
| Predicate | raceClassOfSuperlativeStakes |
P131338
|
FINISHED |
| Object | Group 2 |
—
|
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: Group 2 | Statement: [Native Trail, raceClassOfSuperlativeStakes, Group 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceClassOfSuperlativeStakes Context triple: [Native Trail, raceClassOfSuperlativeStakes, Group 2]
-
A.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
B.
raceTypeWon
Indicates the specific type or category of race that an entity has won.
-
C.
raceTypeDetail
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
D.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
E.
raceTrack
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa342a881909afcd995405027af |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:36 a.m.