Triple
T23373899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angels Advocate Tour |
E593552
|
entity |
| Predicate | featuredHitsAndFanFavorites |
P144428
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Angels Advocate Tour, featuredHitsAndFanFavorites, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredHitsAndFanFavorites Context triple: [Angels Advocate Tour, featuredHitsAndFanFavorites, true]
-
A.
featuresGreatestHits
chosen
Indicates that an entity (such as a media item, collection, or product) includes or highlights a selection of the most popular or successful works associated with another entity.
-
B.
hasFanFavoriteTrack
Indicates that an entity is associated with a track that is especially popular or favored by fans.
-
C.
isFanFavorite
Indicates that an entity is especially popular or well-liked among fans compared to others.
-
D.
liveFavoriteOf
Indicates that one entity is the preferred or most favored choice of another in a live or real-time context.
-
E.
featuredSongPerformancesFrom
Indicates that certain song performances are highlighted or prominently presented as originating from a particular source, event, or context.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b0bc3c8190b1093f7ea29d015c |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:33 p.m.