Triple
T23528518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Summer Tour |
E576498
|
entity |
| Predicate | mainlyPerformed |
P153122
|
FINISHED |
| Object | Grateful Dead 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: Grateful Dead songs | Statement: [2022 Summer Tour, mainlyPerformed, Grateful Dead songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainlyPerformed Context triple: [2022 Summer Tour, mainlyPerformed, Grateful Dead songs]
-
A.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
B.
performed
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
-
C.
performsPrimarilyIn
Indicates that an entity (such as a performer or group) mainly carries out its performances within a particular location, medium, or context.
-
D.
commonlyPerformedAs
Indicates that an action, behavior, or role is typically or frequently carried out in a particular manner, form, or context.
-
E.
commonlyPerformedIn
Indicates that an action or activity is typically or frequently carried out within a particular context, location, or setting.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac758038819098f5f597be39274e |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:09 p.m.