Triple
T6850441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Tour |
E158000
|
entity |
| Predicate | rankingPointsAwarded |
P26152
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ATP Tour, rankingPointsAwarded, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingPointsAwarded Context triple: [ATP Tour, rankingPointsAwarded, yes]
-
A.
rankingPoints
chosen
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
B.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation system.
-
C.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
D.
rankingMember
Indicates that one entity is the highest-ranking or most senior member within a particular group, committee, or organization relative to the others.
-
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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84c45708190918adfc028252400 |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.