Triple
T33295951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern soul |
E852446
|
entity |
| Predicate | associatedRecordingStudio |
P48509
|
FINISHED |
| Object | Stax studio |
E314349
|
NE 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: Stax studio | Statement: [Southern soul, associatedRecordingStudio, Stax studio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRecordingStudio Context triple: [Southern soul, associatedRecordingStudio, Stax studio]
-
A.
hasRecordingStudio
chosen
Indicates that an entity possesses, operates, or is associated with a recording studio.
-
B.
associatedWithArtistStudio
Indicates that an entity has a relationship or connection to a particular artist’s studio, such as being located in, created in, or otherwise linked to that studio.
-
C.
closedAsRecordingStudio
Indicates that an entity ceased operating specifically in its function as a recording studio.
-
D.
ownedStudio
Indicates that one entity possessed ownership or controlling interest in a particular studio.
-
E.
academyAwardForBestSoundRecordingStudio
Indicates that an entity received the Academy Award specifically for excellence in sound recording achieved at a particular studio.
- F. None of above.
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_69f34966ed4c81908dc9dda82d8c7fe3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35431d6b808190a79254067989ac6b |
completed | June 19, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:33 a.m.