Triple
T34069003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cryin' |
E873711
|
entity |
| Predicate | isPartOfTourSetlistFor |
P33226
|
FINISHED |
| Object | Vixen 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: Vixen tours | Statement: [Cryin', isPartOfTourSetlistFor, Vixen tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfTourSetlistFor Context triple: [Cryin', isPartOfTourSetlistFor, Vixen tours]
-
A.
featuredInTourSetlistOf
chosen
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
-
B.
recordsTour
Indicates that an entity documents or logs information about a tour, such as its details, occurrences, or progress.
-
C.
hasSetlistScope
Indicates that a setlist is associated with, or limited to, a particular scope or context (such as a specific event, tour, or performance).
-
D.
hasSetlistSource
Indicates that a setlist is derived from, documented by, or associated with a particular source or reference.
-
E.
hasSetlistItem
Indicates that something (typically a performance or event) includes a specific item as part of its setlist or ordered program.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: May 1, 2026, 1:52 a.m.