Triple
T34094709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premio Nacional de Danza |
E874392
|
entity |
| Predicate | beneficiarios |
P7910
|
FINISHED |
| Object | creadores de danza |
—
|
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: creadores de danza | Statement: [Premio Nacional de Danza, beneficiarios, creadores de danza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beneficiarios Context triple: [Premio Nacional de Danza, beneficiarios, creadores de danza]
-
A.
beneficiaries
chosen
Indicates that certain entities receive advantages, profits, or positive outcomes from an action, event, or arrangement.
-
B.
eligibleBeneficiaries
Indicates that certain parties meet the required conditions to receive benefits or entitlements under a given rule or program.
-
C.
primaryBeneficiaries
Indicates which entities are the main recipients or advantaged parties resulting from a particular action, resource, or arrangement.
-
D.
estimatedNumberOfBeneficiaries
Indicates the approximate count of individuals or entities expected to receive benefits from something.
-
E.
beneficialMembers
Indicates that certain members of a group have a positive or advantageous effect on the group or on other entities.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f731cc6d1881908f80386ef4d70a09 |
completed | May 3, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69f7317779e08190bf85777578221a6b |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:52 a.m.