Triple
T24902909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITF Pace Category 3 (medium) |
E623627
|
entity |
| Predicate | hasPaceRange |
P140422
|
FINISHED |
| Object | medium |
—
|
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: medium | Statement: [ITF Pace Category 3 (medium), hasPaceRange, medium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaceRange Context triple: [ITF Pace Category 3 (medium), hasPaceRange, medium]
-
A.
hasPaceGroups
Indicates that an event or activity is organized into distinct groups based on participants’ pace or speed.
-
B.
hasSpeedRegime
chosen
Indicates a relationship where an entity is associated with a particular speed range or operating speed condition under which it functions or is evaluated.
-
C.
governingSpeedRange
Indicates the range of speeds within which a governing or limiting mechanism is intended to operate or apply.
-
D.
hasSpeedLimitRange
Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
-
E.
hasCadence
Indicates that something possesses or exhibits a particular rhythmic pattern, tempo, or flow.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 5:27 a.m.