Triple
T23625735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League 2013–14 |
E583458
|
entity |
| Predicate | nicknameOfTitle |
P140072
|
FINISHED |
| Object | La Décima |
—
|
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: La Décima | Statement: [UEFA Champions League 2013–14, nicknameOfTitle, La Décima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameOfTitle Context triple: [UEFA Champions League 2013–14, nicknameOfTitle, La Décima]
-
A.
hasTitleNickname
chosen
Indicates that an entity is known by or referred to using a particular title-style nickname.
-
B.
namedForTitle
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
-
C.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
D.
traditionalTitleGivenBy
Indicates that one entity has conferred or assigned a traditional or customary title to another entity.
-
E.
epithetOrTitle
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17c993c8190bf9ee3201869d240 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.