Triple
T9041023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnin’ Train |
E216626
|
entity |
| Predicate | hasStudioAlbumNumberOfArtist |
P27806
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Burnin’ Train, hasStudioAlbumNumberOfArtist, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudioAlbumNumberOfArtist Context triple: [Burnin’ Train, hasStudioAlbumNumberOfArtist, 20]
-
A.
hasStudioAlbum
Indicates that an entity (typically an artist) is associated with or has released a particular studio album.
-
B.
numberInArtistStudioAlbums
chosen
Indicates the count of studio albums an artist has released or is associated with.
-
C.
hasStudioAlbumContext
Indicates that there is a contextual relationship between an entity and a specific studio album, such as information, metadata, or circumstances associated with that album.
-
D.
hasStudioAlbumSequence
Indicates the ordered sequence in which a subject’s studio albums are released or arranged relative to one another.
-
E.
hasArtist
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b100a348190a59abd6e9b815c63 |
completed | April 1, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.