Triple
T3651712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearls: Songs of Goffin and King |
E77430
|
entity |
| Predicate | periodOfRecording |
P44812
|
FINISHED |
| Object | late 1970s |
—
|
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: late 1970s | Statement: [Pearls: Songs of Goffin and King, periodOfRecording, late 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfRecording Context triple: [Pearls: Songs of Goffin and King, periodOfRecording, late 1970s]
-
A.
mainRecordingPeriod
chosen
Indicates the primary time span during which the recording activity took place.
-
B.
recordingPeriodRequirement
Indicates the required duration or time period over which records or data must be kept or maintained.
-
C.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b664448190986b5223d59de282 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.