Triple
T15133740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stranger at the Table |
E361494
|
entity |
| Predicate | recordedForReleaseType |
P15615
|
FINISHED |
| Object | mixtape |
—
|
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: mixtape | Statement: [Stranger at the Table, recordedForReleaseType, mixtape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedForReleaseType Context triple: [Stranger at the Table, recordedForReleaseType, mixtape]
-
A.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
-
B.
recordedInRelease
Indicates that an audio or media recording is included as part of a specific release (such as an album, single, or edition).
-
C.
recordingFor
Indicates that one entity serves as a recorded representation (such as audio, video, or data capture) created for, or documenting, another entity or event.
-
D.
recordingType
chosen
Indicates the specific kind or category of recording associated with an entity (e.g., audio, video, live, studio, etc.).
-
E.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b29a4c819087f8818e3f5788f5 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.