Triple
T24489555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Open women’s doubles champion |
E617603
|
entity |
| Predicate | associatedRankingImpact |
P23822
|
FINISHED |
| Object | affects WTA doubles rankings |
—
|
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: affects WTA doubles rankings | Statement: [US Open women’s doubles champion, associatedRankingImpact, affects WTA doubles rankings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRankingImpact Context triple: [US Open women’s doubles champion, associatedRankingImpact, affects WTA doubles rankings]
-
A.
rankingImpact
chosen
Indicates how an entity’s position or level in a ranking is affected or influenced by another factor or action.
-
B.
relatedRanking
Indicates a relationship where one item’s ranking is connected to or influenced by another item’s ranking.
-
C.
associatedWithRank
Indicates a relationship where an entity is linked to a specific rank, level, or hierarchical position.
-
D.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
E.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:22 a.m.