Triple
T4867393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Albums Chart top 5 |
E109003
|
entity |
| Predicate | orderingCriterion |
P48210
|
FINISHED |
| Object | highest to lowest consumption |
—
|
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: highest to lowest consumption | Statement: [UK Albums Chart top 5, orderingCriterion, highest to lowest consumption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderingCriterion Context triple: [UK Albums Chart top 5, orderingCriterion, highest to lowest consumption]
-
A.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
B.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
C.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
D.
originallyOrderedBy
Indicates that one entity was the initial source or originator of an order or request for another entity.
-
E.
listingCriterion
chosen
Indicates the rule or standard used to determine how items are selected, ordered, or displayed in a listing.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d7bb0b88190bbc24498619910fc |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.