Triple
T2700710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AC/DC |
E59220
|
entity |
| Predicate | hasAlbumSales |
P42069
|
FINISHED |
| Object | over 200 million records worldwide |
—
|
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: over 200 million records worldwide | Statement: [AC/DC, hasAlbumSales, over 200 million records worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlbumSales Context triple: [AC/DC, hasAlbumSales, over 200 million records worldwide]
-
A.
hasLiveAlbum
Indicates that an artist or musical act has released at least one live album recording.
-
B.
hasDiscographyType
Indicates that an entity’s discography is classified as a specific type (such as studio albums, live albums, compilations, etc.).
-
C.
hasNotableAlbum
Indicates that an entity (typically a musical artist or group) is associated with one or more albums that are considered notable or significant.
-
D.
hasSoloAlbum
Indicates that an individual has released at least one music album as a solo artist, separate from any group or band projects.
-
E.
hasPartInDiscography
Indicates that an entity (such as a song, album, or track) is included as a component within another entity’s discography.
- F. None of above. chosen
Provenance (4 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda4c8d34819094f5e4cbc5a4bb9b |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd9ceec708190aa162399023b2273 |
completed | March 7, 2026, 7:54 a.m. |
Created at: March 6, 2026, 9:55 p.m.