Triple
T37252956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chesky Records |
E924041
|
entity |
| Predicate | recordingPhilosophy |
P89583
|
FINISHED |
| Object | no overdubs |
—
|
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: no overdubs | Statement: [Chesky Records, recordingPhilosophy, no overdubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingPhilosophy Context triple: [Chesky Records, recordingPhilosophy, no overdubs]
-
A.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
B.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
-
C.
recordingFor
Indicates that one entity serves as a recorded representation (such as audio, video, or data capture) created for, or documenting, another entity or event.
-
D.
recordingStyle
chosen
Indicates the manner or technique used to capture or document something, such as audio, video, or data.
-
E.
recordingMethod
Indicates the technique or process used to capture or record something (such as data, audio, or video).
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:15 p.m.