Triple
T32183450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCI5*-L |
E822043
|
entity |
| Predicate | dressageFeature |
P173290
|
FINISHED |
| Object | most advanced eventing dressage tests |
—
|
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: most advanced eventing dressage tests | Statement: [CCI5*-L, dressageFeature, most advanced eventing dressage tests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dressageFeature Context triple: [CCI5*-L, dressageFeature, most advanced eventing dressage tests]
-
A.
featuresHorse
Indicates that something includes, presents, or prominently involves a horse as a central element or subject.
-
B.
horseSport
Indicates a relationship where an activity or sport specifically involves the participation or use of horses.
-
C.
horseEquipment
Indicates that one entity is equipment or gear specifically used for or associated with a horse.
-
D.
hasRacecourseFeature
Indicates that something possesses or includes a specific feature or characteristic related to a racecourse.
-
E.
horseDirection
Indicates the direction in which a horse is oriented or moving relative to a reference point or path.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bab75a948190a531ac204aee4fca |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b42902a081909126c7322858a2b3 |
completed | May 3, 2026, 2:34 a.m. |
Created at: May 1, 2026, 12:34 a.m.