Triple
T24902575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Tour 250 |
E623619
|
entity |
| Predicate | tourLevelBelow |
P10194
|
FINISHED |
| Object | ATP Tour 500 |
—
|
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 Tour 500 | Statement: [ATP Tour 250, tourLevelBelow, ATP Tour 500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourLevelBelow Context triple: [ATP Tour 250, tourLevelBelow, ATP Tour 500]
-
A.
tourLevel
Indicates the relative difficulty, expertise, or experience level associated with a particular tour or guided activity.
-
B.
typicalLowestLevel
Indicates that something represents the most basic or minimal level that is commonly or normally found within a given context.
-
C.
membershipLevelBelow
Indicates that one entity’s membership level is ranked lower or less privileged than another entity’s membership level.
-
D.
belowLeague
chosen
Indicates that one entity is in a lower league, division, or competitive tier than another entity.
-
E.
trimLevelBelow
Indicates that one entity’s trim level is lower or less equipped than another entity’s trim level.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:27 a.m.