Triple
T30916376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP |
E787588
|
entity |
| Predicate | usesRankingSystemFor |
P12770
|
FINISHED |
| Object | tournament entry |
—
|
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: tournament entry | Statement: [ATP, usesRankingSystemFor, tournament entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRankingSystemFor Context triple: [ATP, usesRankingSystemFor, tournament entry]
-
A.
usesRankingPoints
Indicates that one entity bases its ordering, evaluation, or decision-making on ranking points associated with another entity.
-
B.
hasRankingSystemManagedBy
Indicates that a ranking system is overseen, controlled, or administered by a specified managing entity.
-
C.
hasRankingAlgorithm
Indicates that an entity uses or is associated with a specific algorithm for ranking or ordering items.
-
D.
usesRank
chosen
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
E.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 29, 2026, 8:51 p.m.