Triple
T29664156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Is Everybody Listening? |
E750484
|
entity |
| Predicate | recordedInThe |
P117505
|
FINISHED |
| Object | mid-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: mid-1970s | Statement: [Is Everybody Listening?, recordedInThe, mid-1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedInThe Context triple: [Is Everybody Listening?, recordedInThe, mid-1970s]
-
A.
reRecordedIn
Indicates that an existing recording of something (e.g., a performance or audio/video content) was made again and captured in a new recording instance.
-
B.
recordedInText
Indicates that an event, fact, or relationship is documented or mentioned within a particular text or written source.
-
C.
oftenRecordedIn
Indicates that instances of one entity are frequently documented, logged, or captured within another entity (such as a medium, dataset, or record).
-
D.
wasRecordedIn
chosen
Indicates that an event, action, or piece of information was documented or captured within a specific record, medium, or recording session.
-
E.
laterRecordedIn
Indicates that the referenced information or event was documented or captured at a later time in the specified source or record.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 28, 2026, 7 p.m.