Triple
T21673929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GRRR! |
E534919
|
entity |
| Predicate | includesRecordingsFromPeriod |
P140004
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [GRRR!, includesRecordingsFromPeriod, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRecordingsFromPeriod Context triple: [GRRR!, includesRecordingsFromPeriod, 1960s]
-
A.
includesRecordingPeriod
chosen
Indicates that one entity encompasses or specifies the time span during which another entity was recorded or observed.
-
B.
recordedBetween
Indicates that an event or data item was recorded at a time that falls within a specified start and end time interval.
-
C.
includesLiveRecordings
Indicates that the subject contains or features recordings captured from live performances rather than studio-produced versions.
-
D.
recordingPeriodRequirement
Indicates the required duration or time period over which records or data must be kept or maintained.
-
E.
mainRecordingPeriod
Indicates the primary time span during which the recording activity took place.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0e06688190a75ea29534f5eed3 |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:41 p.m.