Triple
T21872382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oasis |
E540037
|
entity |
| Predicate | hasCoverArtType |
P24958
|
FINISHED |
| Object | visual representation of tranquil or mystical landscape |
—
|
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: visual representation of tranquil or mystical landscape | Statement: [Oasis, hasCoverArtType, visual representation of tranquil or mystical landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverArtType Context triple: [Oasis, hasCoverArtType, visual representation of tranquil or mystical landscape]
-
A.
hasCoverArtSource
Indicates that an entity’s cover art is derived from, or visually based on, another specified source entity.
-
B.
hasCoverArtVariant
Indicates that an item has an alternative version of its cover artwork distinct from the primary cover.
-
C.
hasCoverArtFeaturing
Indicates that one entity’s cover art visually features or depicts another entity.
-
D.
hasCoverArtTheme
chosen
Indicates that an item’s cover art visually represents or is characterized by a particular theme or motif.
-
E.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f3368d488190a37224b587858ab0 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:59 p.m.