Triple
T24902780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebound Ace |
E623623
|
entity |
| Predicate | governingBodyCertification |
P13210
|
FINISHED |
| Object | ITF classified hardcourt |
—
|
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 classified hardcourt | Statement: [Rebound Ace, governingBodyCertification, ITF classified hardcourt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyCertification Context triple: [Rebound Ace, governingBodyCertification, ITF classified hardcourt]
-
A.
certificationBy
chosen
Indicates that one entity formally attests to, approves, or validates the qualifications, standards, or authenticity of another entity.
-
B.
certificationBasis
Indicates the standard, criteria, or authority on which a certification or official approval is founded.
-
C.
typeOfCertification
Indicates the specific kind or category of certification associated with an entity.
-
D.
hasCertificationStandard
Indicates that an entity complies with, or is associated with, a specific certification standard.
-
E.
governingBodyIncludes
Indicates that a governing body has a particular entity as one of its members or constituent parts.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 18, 2026, 5:27 a.m.