Triple
T31900350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loan Me a Dime |
E814402
|
entity |
| Predicate | recordingPlace |
P8088
|
FINISHED |
| Object | Sheffield, Alabama |
—
|
NE NERFINISHED |
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: Sheffield, Alabama | Statement: [Loan Me a Dime, recordingPlace, Sheffield, Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingPlace Context triple: [Loan Me a Dime, recordingPlace, Sheffield, Alabama]
-
A.
placeOfRecording
chosen
Indicates the location where an audio, video, or other recording was made.
-
B.
widelyRecordedIn
Indicates that an event, fact, or phenomenon has been documented or captured in many different records, sources, or media.
-
C.
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.
-
D.
recordedInText
Indicates that an event, fact, or relationship is documented or mentioned within a particular text or written source.
-
E.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 30, 2026, 11:59 p.m.