Triple
T24902941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITF Pace Category 3 (medium) |
E623627
|
entity |
| Predicate | hasTestingStandard |
P104307
|
FINISHED |
| Object | ITF Court Pace Rating (CPR) test |
—
|
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: ITF Court Pace Rating (CPR) test | Statement: [ITF Pace Category 3 (medium), hasTestingStandard, ITF Court Pace Rating (CPR) test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTestingStandard Context triple: [ITF Pace Category 3 (medium), hasTestingStandard, ITF Court Pace Rating (CPR) test]
-
A.
testedToStandard
chosen
Indicates that something has been evaluated or examined to verify it meets a specified standard or set of criteria.
-
B.
hasSoftwareStandard
Indicates that an entity conforms to, implements, or is governed by a specified software-related standard.
-
C.
hasProductionStandard
Indicates that something is governed, defined, or evaluated according to a specific production standard.
-
D.
hasCertificationStandard
Indicates that an entity complies with, or is associated with, a specific certification standard.
-
E.
hasAssociatedStandard
Indicates that something is linked to or governed by a particular standard or set of standards.
- 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_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:27 a.m.