Triple
T24711425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live at Birdland |
E612035
|
entity |
| Predicate | containsStudioRecordings |
P131543
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Live at Birdland, containsStudioRecordings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsStudioRecordings Context triple: [Live at Birdland, containsStudioRecordings, true]
-
A.
hasStudioRecordings
chosen
Indicates that one entity possesses or is associated with studio-made audio recordings of another entity.
-
B.
hasStudioRecordingComponent
Indicates that one entity is a studio recording component or part of another entity.
-
C.
recordedForStudio
Indicates that a recording was made specifically for, or under contract with, a particular studio.
-
D.
includesRecordingsBy
Indicates that one entity (such as a collection, album, or compilation) contains or features recordings created or performed by another entity (such as an artist or group).
-
E.
containsEarlyBandRecordings
Indicates that something includes recordings made by a band during its early period or formative years.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 3:24 a.m.