Triple
T31365553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1001 Albums You Must Hear Before You Die |
E799998
|
entity |
| Predicate | numberOfItemsListed |
P120121
|
FINISHED |
| Object | 1001 |
—
|
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: 1001 | Statement: [1001 Albums You Must Hear Before You Die, numberOfItemsListed, 1001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfItemsListed Context triple: [1001 Albums You Must Hear Before You Die, numberOfItemsListed, 1001]
-
A.
estimatedNumberOfItems
chosen
Indicates the approximate count or quantity of items associated with the subject, typically when the exact number is unknown or uncertain.
-
B.
isListing
Indicates that an entity functions as a listing, typically representing an item, service, or offering that is being presented, advertised, or made available.
-
C.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
D.
hasListingNumber
Indicates that an entity is associated with a specific listing identification number.
-
E.
mainQuantity
Indicates that the associated value represents the primary or principal quantity in a given context or relationship.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00d24043e8819090cc473b6c0923d0 |
completed | May 10, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_6a00d1ec12fc81908c514ed088ef8300 |
completed | May 10, 2026, 6:43 p.m. |
Created at: April 29, 2026, 9:18 p.m.