Triple
T32115707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | k.d. lang and the Reclines |
E820232
|
entity |
| Predicate | supportedRecordingPeriod |
P145388
|
FINISHED |
| Object | early recordings of k.d. lang |
—
|
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: early recordings of k.d. lang | Statement: [k.d. lang and the Reclines, supportedRecordingPeriod, early recordings of k.d. lang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedRecordingPeriod Context triple: [k.d. lang and the Reclines, supportedRecordingPeriod, early recordings of k.d. lang]
-
A.
includesRecordingPeriod
Indicates that one entity encompasses or specifies the time span during which another entity was recorded or observed.
-
B.
mainRecordingPeriod
Indicates the primary time span during which the recording activity took place.
-
C.
recordingPeriodRequirement
Indicates the required duration or time period over which records or data must be kept or maintained.
-
D.
capturesPeriod
chosen
Indicates that one entity records, encompasses, or represents a specific span of time associated with another entity.
-
E.
recordDuration
Indicates the length of time for which something is recorded or captured.
- 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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:28 a.m.