Triple
T28963708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VH1 100 Greatest Songs of the 80s |
E731978
|
entity |
| Predicate | listOrdering |
P164829
|
FINISHED |
| Object | ranked from 100 to 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: ranked from 100 to 1 | Statement: [VH1 100 Greatest Songs of the 80s, listOrdering, ranked from 100 to 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listOrdering Context triple: [VH1 100 Greatest Songs of the 80s, listOrdering, ranked from 100 to 1]
-
A.
orderingType
chosen
Indicates the specific method or arrangement by which items, events, or entities are ordered or sequenced relative to one another.
-
B.
ordersBy
Indicates that one entity arranges, sorts, or sequences another entity according to a specified criterion or set of criteria.
-
C.
displayOrder
Indicates the sequence or position in which items should be presented or shown relative to one another.
-
D.
orderName
Indicates the designated name or label assigned to a specific order in a transaction or ordering process.
-
E.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65c2ae94c8190a6a524800686ef66 |
completed | May 2, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:51 a.m.