Triple
T33519797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relaxed Muscle |
E858468
|
entity |
| Predicate | hasLiveAppearanceWith |
P83295
|
FINISHED |
| Object | Jarvis Cocker solo shows |
—
|
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: Jarvis Cocker solo shows | Statement: [Relaxed Muscle, hasLiveAppearanceWith, Jarvis Cocker solo shows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveAppearanceWith Context triple: [Relaxed Muscle, hasLiveAppearanceWith, Jarvis Cocker solo shows]
-
A.
hasPublicAppearancesWith
Indicates that two entities have appeared together in public settings or events.
-
B.
hasLivePerformanceWith
chosen
Indicates that two or more entities participate together in the same live performance event.
-
C.
hasNotableLivePerformancesBy
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
-
D.
hasPerformedLiveIn
Indicates that an entity has given a live performance in a specified location or venue.
-
E.
hasLiveAlbumAppearanceOrder
Indicates the sequential position in which an entity appears on a live album’s track listing or performance order.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 1, 2026, 1:39 a.m.