Triple
T29000080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucero |
E736273
|
entity |
| Predicate | knownForLiveShows |
P173392
|
FINISHED |
| Object | energetic performances |
—
|
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: energetic performances | Statement: [Lucero, knownForLiveShows, energetic performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForLiveShows Context triple: [Lucero, knownForLiveShows, energetic performances]
-
A.
knownForFeaturing
Indicates that one entity is notable or recognized for prominently including, presenting, or showcasing another entity.
-
B.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
C.
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.
-
D.
notableLivePerformanceEvent
Indicates that an entity is a significant or widely recognized live performance event associated with another entity (such as an artist, work, or venue).
-
E.
knownForAct
Indicates that an entity is recognized or notable for performing a particular act or action.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 28, 2026, 9:34 a.m.