Triple
T25272879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Something to Live For |
E633612
|
entity |
| Predicate | isRecordedInMedium |
P117505
|
FINISHED |
| Object | live jazz performances |
—
|
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: live jazz performances | Statement: [Something to Live For, isRecordedInMedium, live jazz performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecordedInMedium Context triple: [Something to Live For, isRecordedInMedium, live jazz performances]
-
A.
wasRecordedIn
chosen
Indicates that an event, action, or piece of information was documented or captured within a specific record, medium, or recording session.
-
B.
recordedInText
Indicates that an event, fact, or relationship is documented or mentioned within a particular text or written source.
-
C.
wasRecordedBy
Indicates that an event, observation, or piece of data was captured or documented by a specific agent, instrument, or recording process.
-
D.
mediatisedBy
Indicates that an entity’s communication or interaction is conveyed, shaped, or influenced through a particular medium or media channel rather than occurring directly.
-
E.
areRecordedBy
Indicates that an event, observation, or piece of information is captured or documented by a specific recording agent, device, or process.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba43d708190bb66243657f44b18 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:17 p.m.