Triple
T24902696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Rankings |
E623621
|
entity |
| Predicate | secondHighestPointsCategory |
P162554
|
FINISHED |
| Object | ATP Masters 1000 tournaments |
—
|
NE NERFINISHED |
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: ATP Masters 1000 tournaments | Statement: [ATP Rankings, secondHighestPointsCategory, ATP Masters 1000 tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondHighestPointsCategory Context triple: [ATP Rankings, secondHighestPointsCategory, ATP Masters 1000 tournaments]
-
A.
isSecondHighest
Indicates that one entity ranks immediately below the highest-ranked entity within a specified ordering or set.
-
B.
secondPlace
Indicates that an entity holds the position of runner-up or finishes in second place in a ranked ordering, competition, or comparison relative to others.
-
C.
secondRunnerUp
Indicates that one entity finished in third place in a competition or ranking relative to the others.
-
D.
secondMostPointsTeam
Indicates that the subject is the team that has the second-highest number of points in a given ranking or competition.
-
E.
secondRank
Indicates that one entity holds the second position or rank in order or hierarchy relative to others.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f627ad6d4c81909796d39d78e414f9 |
completed | May 2, 2026, 4:34 p.m. |
Created at: April 18, 2026, 5:27 a.m.