Triple
T16056928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catching Tales |
E389503
|
entity |
| Predicate | includesCoverVersions |
P11142
|
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: [Catching Tales, includesCoverVersions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCoverVersions Context triple: [Catching Tales, includesCoverVersions, true]
-
A.
hasCoverVersions
chosen
Indicates that a musical work has one or more recorded versions performed or produced by artists other than the original creator.
-
B.
officialVersionIncludes
Indicates that an official or authoritative version of something contains, incorporates, or encompasses a specified component, element, or subset.
-
C.
alsoCovers
Indicates that something extends its scope or applicability to include an additional subject, area, or case beyond what was originally covered.
-
D.
coverVersionBy
Indicates that one creative work is a cover version performed or produced by a particular artist or entity.
-
E.
providesCoverage
Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.