Triple
T15226350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Honey |
E363887
|
entity |
| Predicate | mainlyRecordedAt |
P8088
|
FINISHED |
| Object | Brian Wilson's home studio |
—
|
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: Brian Wilson's home studio | Statement: [Wild Honey, mainlyRecordedAt, Brian Wilson's home studio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainlyRecordedAt Context triple: [Wild Honey, mainlyRecordedAt, Brian Wilson's home studio]
-
A.
mainlyRecordedDuring
Indicates that an event, activity, or phenomenon was predominantly documented or captured within a specific time period or context.
-
B.
mainlyRecordedBy
Indicates that the primary or most significant recording of something (such as a work, event, or data set) was made by a particular agent or entity.
-
C.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
-
D.
placeOfRecording
chosen
Indicates the location where an audio, video, or other recording was made.
-
E.
recordedOnDate
Indicates the specific calendar date on which an event, action, or piece of information was formally recorded.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078bb32881909927561c6c072546 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.