Triple
T7020031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackheart Man |
E162795
|
entity |
| Predicate | isOftenListedIn |
P46711
|
FINISHED |
| Object | greatest reggae albums lists |
—
|
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: greatest reggae albums lists | Statement: [Blackheart Man, isOftenListedIn, greatest reggae albums lists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenListedIn Context triple: [Blackheart Man, isOftenListedIn, greatest reggae albums lists]
-
A.
isFrequentlyIncludedIn
chosen
Indicates that something is regularly or commonly contained or made part of something else.
-
B.
isListedBy
Indicates that one entity appears as an item or entry in a list, catalog, or register maintained or provided by another entity.
-
C.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
D.
isListedEntityThrough
Indicates that one entity is recognized or recorded as a listed entity by means of, or via the involvement of, another entity or mechanism.
-
E.
listedOn
Indicates that an item, entity, or piece of information appears as an entry on a particular list, platform, or catalog.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:34 p.m.