Triple
T32664988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Make It Mine |
E835132
|
entity |
| Predicate | featuresVocalImprovisation |
P203145
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Make It Mine, featuresVocalImprovisation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresVocalImprovisation Context triple: [Make It Mine, featuresVocalImprovisation, true]
-
A.
featuresVocal
Indicates that one entity includes or presents the vocal performance or voice of another entity.
-
B.
featuresVocalPercussion
Indicates that the subject includes or makes use of vocal percussion (such as beatboxing or mouth-made rhythmic sounds) as part of its content or performance.
-
C.
featuresVocalHarmonyBy
Indicates that the subject work includes vocal harmony performances contributed by the specified artist or group.
-
D.
featuresVocalChant
Indicates that the subject includes or contains vocal chanting as a prominent element or component.
-
E.
vocalTraining
Indicates that one entity provides or engages in training aimed at improving another entity’s vocal or singing abilities.
- F. None of above. chosen
Provenance (4 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a01289f781481908f3788f8a719f2f4 |
completed | May 11, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a012823c7248190961e20be48dd6246 |
completed | May 11, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_6a01289ecf7481908802642bb4399ac0 |
completed | May 11, 2026, 12:53 a.m. |
Created at: May 1, 2026, 1:08 a.m.