Triple
T26186853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renaissance |
E654851
|
entity |
| Predicate | hasNotableLiveRelease |
P136559
|
FINISHED |
| Object | Live at Carnegie Hall |
—
|
NE NERFINISHED |
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: Live at Carnegie Hall | Statement: [Renaissance, hasNotableLiveRelease, Live at Carnegie Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLiveRelease Context triple: [Renaissance, hasNotableLiveRelease, Live at Carnegie Hall]
-
A.
hasNotableReleaseArtist
Indicates that an entity (such as a release or work) is associated with a notable artist responsible for its creation or performance.
-
B.
hasLiveSingleRelease
Indicates that an entity has released a live recording of a single as an official release.
-
C.
hasLiveVideoRelease
chosen
Indicates that an entity has an associated release of a live video recording.
-
D.
hasNotableVersion
Indicates that an entity has a specific version or variant that is particularly significant, distinguished, or noteworthy compared to other versions.
-
E.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 26, 2026, 8:42 p.m.