Triple
T16953873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DJ Mag Top 100 DJs number 1 |
E411246
|
entity |
| Predicate | hasRankingPosition |
P113769
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [DJ Mag Top 100 DJs number 1, hasRankingPosition, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankingPosition Context triple: [DJ Mag Top 100 DJs number 1, hasRankingPosition, 1]
-
A.
hasRankingCategory
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
-
B.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
C.
roleInRanking
chosen
Indicates that an entity holds a specific position or function within a particular ranking or ordered list.
-
D.
rankingPositions
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
-
E.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01b04e88190a72735541b3bb117 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.