Triple
T13001292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSI 2* |
E322174
|
entity |
| Predicate | horseEligibility |
P96062
|
FINISHED |
| Object | registered with a national federation |
—
|
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: registered with a national federation | Statement: [CSI 2*, horseEligibility, registered with a national federation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: horseEligibility Context triple: [CSI 2*, horseEligibility, registered with a national federation]
-
A.
eligibleHorses
chosen
Indicates that certain horses meet the required conditions or criteria to qualify for a specified status, event, or action.
-
B.
horseName
Indicates that an entity has the specified name of a horse.
-
C.
usesHorseType
Indicates that one entity employs, relies on, or operates using a specific type or category of horse.
-
D.
qualifyingFor
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
-
E.
hasNotableHorse
Indicates that an entity is associated with a horse that is considered notable or distinguished in some recognized way.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9828748190b2ad9ea29180b7d3 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:47 p.m.