Triple
T36780218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern soul |
E908745
|
entity |
| Predicate | typicalRecordingPeriod |
P84192
|
FINISHED |
| Object | mid-1960s American soul 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: mid-1960s American soul recordings | Statement: [Northern soul, typicalRecordingPeriod, mid-1960s American soul recordings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRecordingPeriod Context triple: [Northern soul, typicalRecordingPeriod, mid-1960s American soul recordings]
-
A.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
B.
typicalPeriod
chosen
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
C.
mainRecordingPeriod
Indicates the primary time span during which the recording activity took place.
-
D.
typicalPeriodRange
Indicates the usual or most commonly observed range of time intervals associated with an event, process, or state.
-
E.
recordingPeriodRequirement
Indicates the required duration or time period over which records or data must be kept or maintained.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.