Triple
T8388407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTA 250 tournaments |
E197877
|
entity |
| Predicate | categoryNameOrigin |
P3325
|
FINISHED |
| Object | named after 250-level prize money tier |
—
|
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: named after 250-level prize money tier | Statement: [WTA 250 tournaments, categoryNameOrigin, named after 250-level prize money tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryNameOrigin Context triple: [WTA 250 tournaments, categoryNameOrigin, named after 250-level prize money tier]
-
A.
speciesOrigin
Indicates the place, environment, or source from which a species originally arose or evolved.
-
B.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
C.
categoryDefinedIn
Indicates that a category is formally specified or established within a particular source, context, or definitional framework.
-
D.
colorOrigin
Indicates the source or cause from which an entity’s color is derived or determined.
-
E.
categoryDefinedBy
Indicates that a category is established, characterized, or delimited according to a specific defining criterion, rule, or source.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb81090f688190a3a8d1680383c361 |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.