Triple
T32115728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | k.d. lang and the Reclines |
E820232
|
entity |
| Predicate | collaborationTypeWithKDlang |
P42125
|
FINISHED |
| Object | studio recordings |
—
|
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: studio recordings | Statement: [k.d. lang and the Reclines, collaborationTypeWithKDlang, studio recordings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationTypeWithKDlang Context triple: [k.d. lang and the Reclines, collaborationTypeWithKDlang, studio recordings]
-
A.
collaborationLanguage
Indicates the language used as the primary medium of communication in a collaboration between entities.
-
B.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
C.
collaborationAspect
chosen
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
-
D.
collaborationModel
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
E.
collaboratesVia
Indicates that two or more entities work together or coordinate their activities through a specified medium, channel, or intermediary.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b908810c8190bd58d2d0eee21d40 |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:28 a.m.