Triple
T28722310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTA Tour |
E730127
|
entity |
| Predicate | hasRankingUpdateFrequency |
P51026
|
FINISHED |
| Object | weekly |
—
|
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: weekly | Statement: [WTA Tour, hasRankingUpdateFrequency, weekly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankingUpdateFrequency Context triple: [WTA Tour, hasRankingUpdateFrequency, weekly]
-
A.
rankingUpdateFrequency
chosen
Indicates how often the ranking or ordered list associated with an entity is recalculated or refreshed.
-
B.
selectionRankingFrequency
Indicates how often an entity is chosen or ranked in a particular position within a selection or ordering process.
-
C.
hasRankingFactor
Indicates that one entity contributes as a factor to determining the ranking or ordered position of another entity.
-
D.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
E.
hasRankingDomain
Indicates that one entity is associated with a specific ranking domain within which its rank or position is evaluated.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 5:54 a.m.