Triple
T22393176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grabación del Año |
E553556
|
entity |
| Predicate | includesCreditTo |
P147478
|
FINISHED |
| Object | featured artists |
—
|
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: featured artists | Statement: [Grabación del Año, includesCreditTo, featured artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCreditTo Context triple: [Grabación del Año, includesCreditTo, featured artists]
-
A.
includesCreditCategory
Indicates that one entity contains or encompasses a specific credit-related category within its defined set or structure.
-
B.
requiresCreditAs
Indicates that one entity must be credited or acknowledged in a specified manner or role in relation to another entity.
-
C.
creditsCanBe
Indicates that certain credits are permitted to be in a specified state, category, or usage condition.
-
D.
creditsUse
Indicates that one entity uses or relies on credits (such as credit units, credit lines, or credit-based resources) provided or available to it.
-
E.
hasCredit
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1585ce39c819082b62e7f2e297d9b |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e73597b51c8190aeff27f4779b82f3 |
completed | April 21, 2026, 8:30 a.m. |
Created at: April 16, 2026, 8:45 p.m.