Triple
T18344487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UAE Derby |
E439498
|
entity |
| Predicate | handicapOrConditions |
P131448
|
FINISHED |
| Object | conditions race |
—
|
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: conditions race | Statement: [UAE Derby, handicapOrConditions, conditions race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handicapOrConditions Context triple: [UAE Derby, handicapOrConditions, conditions race]
-
A.
handicap
Indicates that one entity imposes or experiences a disadvantage, constraint, or limiting condition in relation to another entity or context.
-
B.
ballCondition
Indicates the specific state or status a ball is in, such as its physical condition, readiness for use, or compliance with required standards.
-
C.
handCondition
Indicates the state or quality of a hand, such as its health, functionality, or any specific condition affecting it.
-
D.
sportRestriction
Indicates a limitation, prohibition, or specific condition placed on participating in a sport or sports-related activity.
-
E.
hasWaterHazards
Indicates that the subject contains or is associated with one or more water-based obstacles or danger areas.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e514f2c8ec8190b045482846a68204 |
completed | April 19, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e4561d665081908ec555344e76d82b |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 10:37 a.m.