Triple
T24971094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP 500 |
E624890
|
entity |
| Predicate | categoryWeightInRankings |
P107592
|
FINISHED |
| Object | medium |
—
|
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: medium | Statement: [ATP 500, categoryWeightInRankings, medium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryWeightInRankings Context triple: [ATP 500, categoryWeightInRankings, medium]
-
A.
rankingCategory
Indicates the classification or type of ranking under which an entity is evaluated or ordered.
-
B.
hasOfficialRankingWeight
chosen
Indicates that something carries an officially recognized weight or importance in determining a ranking or ordered list.
-
C.
hasRankingCategory
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
-
D.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:01 a.m.