Triple
T24971083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP 500 |
E624890
|
entity |
| Predicate | pointDistributionBasis |
P157881
|
FINISHED |
| Object | tournament category |
—
|
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: tournament category | Statement: [ATP 500, pointDistributionBasis, tournament category]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointDistributionBasis Context triple: [ATP 500, pointDistributionBasis, tournament category]
-
A.
boundaryBasis
Indicates that one entity serves as a foundational or defining boundary for another entity.
-
B.
usesBasisFunctions
Indicates that one entity represents, models, or computes another entity by expressing it as a combination of specified basis functions.
-
C.
pointDefinition
Indicates that one entity serves as the defining description or specification of a particular point in another entity.
-
D.
formsBasis
Indicates that one entity serves as the foundational support, justification, or underlying principle upon which another entity is built, derived, or depends.
-
E.
pointSource
Indicates that an entity acts as a localized origin or emitter of some quantity (such as light, sound, or radiation) concentrated at a single point in space.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 6:01 a.m.