Triple
T33472462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hallelujah – Live |
E857232
|
entity |
| Predicate | includesLivePerformancesBy |
P24795
|
FINISHED |
| Object | Espen Lind |
E241638
|
NE 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: Espen Lind | Statement: [Hallelujah – Live, includesLivePerformancesBy, Espen Lind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLivePerformancesBy Context triple: [Hallelujah – Live, includesLivePerformancesBy, Espen Lind]
-
A.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
B.
hasLivePerformanceRole
Indicates that an entity holds or fulfills a specific role in a live performance.
-
C.
hasNotableLivePerformancesWith
Indicates that two entities have shared notable live performances together, such as concerts, shows, or events where they appeared or performed jointly.
-
D.
hasNotableLivePerformancesBy
chosen
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
-
E.
hasLivePerformanceComponent
Indicates that something includes or involves a live performance as a significant component or feature.
- F. None of above.
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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a03232efd8481908ee25447a29ee20b |
completed | May 12, 2026, 12:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a402b887e60819099b602124cd415db |
completed | June 27, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_6a032269dcb08190907c965c28145b77 |
completed | May 12, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:37 a.m.