Triple
T25481452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gala de la Reina |
E638585
|
entity |
| Predicate | mainTitleAwarded |
P2680
|
FINISHED |
| Object | Carnival Queen of Las Palmas de Gran Canaria |
—
|
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: Carnival Queen of Las Palmas de Gran Canaria | Statement: [Gala de la Reina, mainTitleAwarded, Carnival Queen of Las Palmas de Gran Canaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTitleAwarded Context triple: [Gala de la Reina, mainTitleAwarded, Carnival Queen of Las Palmas de Gran Canaria]
-
A.
awardsTitle
chosen
Indicates that an entity confers or grants a specific title or honorific designation to another entity.
-
B.
mainAwardWinner
Indicates that the subject is the primary recipient of a specified award or honor.
-
C.
majorTitleWon
Indicates that an entity has won a significant or top-level title, championship, or major award in a given domain.
-
D.
firstTitleForWinner
Indicates that the associated title is the first title ever won by the specified winner.
-
E.
holderAwardedFor
Indicates that an award holder received the award specifically in recognition of, or as a result of, a particular work, achievement, or contribution.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f77658dc8190975f60eb762b25d5 |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 2:31 p.m.