Triple
T9109957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love, You’re So Beautiful Tonight |
E218572
|
entity |
| Predicate | isStudioRecording |
P86545
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Love, You’re So Beautiful Tonight, isStudioRecording, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStudioRecording Context triple: [Love, You’re So Beautiful Tonight, isStudioRecording, true]
-
A.
isLiveRecording
Indicates that the recording was captured during a live performance or event rather than produced in a studio or through post-production.
-
B.
hasRecordingStudio
Indicates that an entity possesses, operates, or is associated with a recording studio.
-
C.
recordedForStudio
Indicates that a recording was made specifically for, or under contract with, a particular studio.
-
D.
usedForRecordingBy
Indicates that something serves as a medium, tool, or device that is employed by an agent to make a recording.
-
E.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
- F. None of above. chosen
Provenance (4 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca845d9b0819084230e7cdd92dee0 |
completed | April 1, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:16 p.m.