Triple
T28878187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yung Berg discography |
E732329
|
entity |
| Predicate | includesWorkUnderName |
P10663
|
FINISHED |
| Object | Yung Berg |
—
|
NE NERFINISHED |
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: Yung Berg | Statement: [Yung Berg discography, includesWorkUnderName, Yung Berg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesWorkUnderName Context triple: [Yung Berg discography, includesWorkUnderName, Yung Berg]
-
A.
hasFullNameInWork
Indicates that an entity is referred to by a specific full name within a particular work or publication.
-
B.
hasGivenNameInWork
Indicates that a work specifies or uses a particular given (first) name for an entity or character.
-
C.
includedWorkOn
Indicates that one entity contains, features, or incorporates another entity as a work or component within it.
-
D.
workIncludes
chosen
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
E.
employedUnder
Indicates that one entity works as an employee under the authority, supervision, or organizational structure 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: April 28, 2026, 7:40 a.m.