Triple
T28218326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velká pardubická steeplechase |
E711379
|
entity |
| Predicate | numberOfObstacles |
P199633
|
FINISHED |
| Object | around 31 |
—
|
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: around 31 | Statement: [Velká pardubická steeplechase, numberOfObstacles, around 31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfObstacles Context triple: [Velká pardubická steeplechase, numberOfObstacles, around 31]
-
A.
numberOfHurdles
Indicates the quantity of hurdles involved in or associated with a particular event, activity, or entity.
-
B.
obstacles
Indicates that one entity presents barriers, hindrances, or impediments that block or restrict another entity’s progress, action, or interaction.
-
C.
commonObstacle
Indicates that two or more entities share the same hindrance, barrier, or difficulty that impedes their progress or goals.
-
D.
hasObstructions
Indicates that one entity is blocking, hindering, or limiting another entity’s movement, function, or access.
-
E.
obstacleHeightCharacteristic
Indicates the characteristic or measured value of an obstacle’s height in relation to a reference level 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
| PDg | Predicate description generation | batch_69ff49f7db2c819094d488d13985334c |
completed | May 9, 2026, 2:51 p.m. |
Created at: April 27, 2026, 10:44 p.m.