Triple
T25727753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smokin’ at the Half Note |
E645154
|
entity |
| Predicate | hasLivePortionRecordedAt |
P150088
|
FINISHED |
| Object | Half Note Club |
—
|
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: Half Note Club | Statement: [Smokin’ at the Half Note, hasLivePortionRecordedAt, Half Note Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivePortionRecordedAt Context triple: [Smokin’ at the Half Note, hasLivePortionRecordedAt, Half Note Club]
-
A.
hasLiveRecordingFrom
chosen
Indicates that a live recording was made of something (e.g., a work, performance, or event) at or from a specified source, venue, or occasion.
-
B.
hasFirstRecordedRegion
Indicates the geographic region where something was first recorded or documented.
-
C.
hasPartStartTime
Indicates the time at which a specific part or segment of an entity, event, or process begins.
-
D.
hasWorkRecordedThere
Indicates that a person or creator has had their work documented, produced, or otherwise officially recorded at a particular place or institution.
-
E.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 21, 2026, 11:07 p.m.