Triple
T17068702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamal at the Penthouse |
E414155
|
entity |
| Predicate | hasRecordingContext |
P37188
|
FINISHED |
| Object | club performance |
—
|
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: club performance | Statement: [Jamal at the Penthouse, hasRecordingContext, club performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingContext Context triple: [Jamal at the Penthouse, hasRecordingContext, club performance]
-
A.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
B.
hasRecordingContract
Indicates that an entity is formally bound by an agreement to produce recordings for another entity, typically a record label or similar organization.
-
C.
hasTrackContext
Indicates that an entity is associated with or occurs within a particular track-related context (such as a specific track, route, or sequence).
-
D.
isLiveRecording
chosen
Indicates that the recording was captured during a live performance or event rather than produced in a studio or through post-production.
-
E.
recordingState
Indicates the current status or condition of an ongoing or potential recording (e.g., whether recording is active, paused, or stopped) between entities.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbbeb2a48190a733a4cc829c16de |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.