Triple
T27578932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chasing Yesterday Tour |
E699529
|
entity |
| Predicate | hasAlbumTypeSupported |
P171430
|
FINISHED |
| Object | studio album |
—
|
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: studio album | Statement: [Chasing Yesterday Tour, hasAlbumTypeSupported, studio album]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlbumTypeSupported Context triple: [Chasing Yesterday Tour, hasAlbumTypeSupported, studio album]
-
A.
hasParentAlbumType
Indicates that an album is associated with a broader or more general album type from which it derives or is categorized.
-
B.
supportsAlbum
Indicates that one entity provides backing, endorsement, or resources for the creation, promotion, or distribution of a specific music album.
-
C.
hasAlbumStyle
Indicates that an album is associated with a particular artistic, musical, or design style.
-
D.
hasTypeOfSupport
Indicates that one entity provides or is associated with a particular kind or category of support in relation to another entity.
-
E.
albumNumberSupported
Indicates that a system or context supports the use, recognition, or handling of album numbers.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 27, 2026, 2:02 p.m.