Triple
T31651586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iga Świątek |
E807742
|
entity |
| Predicate | rankingAchieved |
P110944
|
FINISHED |
| Object | WTA world No. 1 in singles |
—
|
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: WTA world No. 1 in singles | Statement: [Iga Świątek, rankingAchieved, WTA world No. 1 in singles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingAchieved Context triple: [Iga Świątek, rankingAchieved, WTA world No. 1 in singles]
-
A.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
B.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
C.
rankingStatus
chosen
Indicates the relative position or level an entity holds within an ordered ranking or hierarchy.
-
D.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
E.
rankingBehind
Indicates that one entity holds a lower or later position than another in an ordered ranking or hierarchy.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 30, 2026, 10:53 p.m.