Triple
T31960991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother Records |
E816037
|
entity |
| Predicate | releasedDebutWorkOf |
P75937
|
FINISHED |
| Object | Debut |
—
|
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: Debut | Statement: [Mother Records, releasedDebutWorkOf, Debut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedDebutWorkOf Context triple: [Mother Records, releasedDebutWorkOf, Debut]
-
A.
debutWork
Indicates the work (such as a book, film, album, or performance) that marks an entity’s first public or professional appearance in a given field.
-
B.
releasedDebutAlbumFor
chosen
Indicates that an entity (such as a record label or distributor) was responsible for releasing another entity’s debut music album.
-
C.
madeProfessionalDebutIn
Indicates the time or event in which an individual first performed or appeared in a professional capacity within a given field or organization.
-
D.
debutWorkReleaseYear
Indicates the calendar year in which an entity’s first published or publicly released work originally came out.
-
E.
firstPublishedWork
Indicates that one work is the earliest piece created or released by a particular creator or 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 12:09 a.m.