Triple
T35208438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concours de Saut International 1* |
E1016604
|
entity |
| Predicate | equestrianDiscipline |
P107769
|
FINISHED |
| Object | jumping |
—
|
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: jumping | Statement: [Concours de Saut International 1*, equestrianDiscipline, jumping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equestrianDiscipline Context triple: [Concours de Saut International 1*, equestrianDiscipline, jumping]
-
A.
horseSport
chosen
Indicates a relationship where an activity or sport specifically involves the participation or use of horses.
-
B.
dressageFeature
Indicates a relationship where something serves as a characteristic, element, or component of a dressage activity, performance, or discipline.
-
C.
horseEquipment
Indicates that one entity is equipment or gear specifically used for or associated with a horse.
-
D.
horseCulture
Indicates a cultural relationship in which horses play a central or defining role in the practices, values, or way of life of a group.
-
E.
hasEquestrianFacility
Indicates that a place or property includes facilities specifically designed for horse-related activities, such as riding, training, or boarding.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.