Triple
T24971084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP 500 |
E624890
|
entity |
| Predicate | minimumPointsForWinner |
P157882
|
FINISHED |
| Object | 500 ranking points |
—
|
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: 500 ranking points | Statement: [ATP 500, minimumPointsForWinner, 500 ranking points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumPointsForWinner Context triple: [ATP 500, minimumPointsForWinner, 500 ranking points]
-
A.
minimumNumberOfGames
Indicates the smallest required count of games that must be played or satisfied in a given context or constraint.
-
B.
numberOfWinsRequired
Indicates the specific count of wins an entity must achieve to meet a defined goal, threshold, or condition.
-
C.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
D.
numberOfRoundsToWin
Indicates the number of rounds an entity must win in a competition or game to be declared the overall winner.
-
E.
minimumNumberOnCourt
Indicates the smallest required number of participants that must be present on the court for play or a rule condition to be satisfied.
- 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.