Triple
T29939752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y, ¿Si Fuera Ella? |
E760462
|
entity |
| Predicate | isPerformedInConcertsOf |
P31571
|
FINISHED |
| Object | Alejandro Sanz tours |
—
|
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: Alejandro Sanz tours | Statement: [Y, ¿Si Fuera Ella?, isPerformedInConcertsOf, Alejandro Sanz tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPerformedInConcertsOf Context triple: [Y, ¿Si Fuera Ella?, isPerformedInConcertsOf, Alejandro Sanz tours]
-
A.
performedInConcertBy
Indicates that an action, piece, or performance was carried out jointly by multiple participants as part of the same concert event.
-
B.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
C.
performsMusicIn
chosen
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
D.
hasFanPerformances
Indicates that an entity has associated performances created or carried out by fans.
-
E.
hasNotableLivePerformancesBy
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67805551c81909e016ae9e3031076 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:22 p.m.