Triple
T29963933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voodoo Song |
E761119
|
entity |
| Predicate | hasWorkingTitleRole |
P64794
|
FINISHED |
| Object | pre-release name of Mi Gente |
—
|
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: pre-release name of Mi Gente | Statement: [Voodoo Song, hasWorkingTitleRole, pre-release name of Mi Gente]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkingTitleRole Context triple: [Voodoo Song, hasWorkingTitleRole, pre-release name of Mi Gente]
-
A.
hasWorkingTitle
chosen
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
-
B.
hasTitleRole
Indicates that an entity holds or is assigned a specific title or role in relation to another entity.
-
C.
hasWorkingTitleStatus
Indicates that an entity currently holds the status of having a provisional or working title rather than a finalized official title.
-
D.
hasWorkTitleElement
Indicates that an entity includes a specific textual component representing a work’s title or part of a work’s title.
-
E.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:29 p.m.