Triple
T32714601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FEI World Cup Dressage |
E836487
|
entity |
| Predicate | usesJudgingSystem |
P164628
|
FINISHED |
| Object | FEI dressage judging rules |
—
|
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: FEI dressage judging rules | Statement: [FEI World Cup Dressage, usesJudgingSystem, FEI dressage judging rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesJudgingSystem Context triple: [FEI World Cup Dressage, usesJudgingSystem, FEI dressage judging rules]
-
A.
usedJudgingSystem
chosen
Indicates that a particular judging or evaluation system was employed to assess or score something.
-
B.
usesBlindJudging
Indicates that an evaluation or competition is conducted without judges knowing the identities of the participants.
-
C.
usesQualificationSystem
Indicates that an entity applies or relies on a specific qualification system as part of its processes or operations.
-
D.
hasJudgingFunction
Indicates that an entity holds a role or capacity to evaluate, assess, or make judgments about another entity or situation.
-
E.
hasJudgingComponent
Indicates that something includes an element of evaluation, assessment, or judgment as part of its structure or process.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c884982c8190a8180dd729cc4f15 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.