Triple
T5368039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Dylan concert setlists |
E103175
|
entity |
| Predicate | includeCoversOf |
P13946
|
FINISHED |
| Object | traditional folk songs |
—
|
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: traditional folk songs | Statement: [Bob Dylan concert setlists, includeCoversOf, traditional folk songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeCoversOf Context triple: [Bob Dylan concert setlists, includeCoversOf, traditional folk songs]
-
A.
alsoCovers
chosen
Indicates that something extends its scope or applicability to include an additional subject, area, or case beyond what was originally covered.
-
B.
isCoverOf
Indicates that one entity functions as a protective or enclosing layer placed over another entity.
-
C.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
D.
collectivelyCovers
Indicates that a group of entities, taken together, fully covers or accounts for a specified set, area, or scope.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd86856f688190a34ab93619bae134 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.