Triple
T31214567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.S. |
E795835
|
entity |
| Predicate | appearsOnDisc |
P1995
|
FINISHED |
| Object | HIStory disc two |
—
|
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: HIStory disc two | Statement: [D.S., appearsOnDisc, HIStory disc two]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsOnDisc Context triple: [D.S., appearsOnDisc, HIStory disc two]
-
A.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
B.
hasPartInDiscography
chosen
Indicates that an entity (such as a song, album, or track) is included as a component within another entity’s discography.
-
C.
mayAppearOn
Indicates that one entity is allowed or able to be shown, featured, or present on another entity (such as a platform, medium, or surface).
-
D.
coveredOnAlbum
Indicates that a song or musical work has been recorded as a cover version and included on a particular album.
-
E.
hasPartInDiscographyOf
Indicates that one entity constitutes a component or item within the discography (recorded works catalog) of another entity.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 29, 2026, 9:10 p.m.