Triple
T14018817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spooky |
E337270
|
entity |
| Predicate | originallyRecordedAs |
P74956
|
FINISHED |
| Object | instrumental |
—
|
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: instrumental | Statement: [Spooky, originallyRecordedAs, instrumental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyRecordedAs Context triple: [Spooky, originallyRecordedAs, instrumental]
-
A.
originallyRecordedFor
Indicates that a work or performance was first recorded with the specific purpose of being used, released, or presented in the context of the target entity.
-
B.
previouslyRecordedBy
Indicates that the subject was recorded or documented at an earlier time by the specified agent or source.
-
C.
originallyPresentedAs
chosen
Indicates that one entity was first introduced, described, or characterized in the form or manner specified by another entity.
-
D.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
-
E.
reRecordedFrom
Indicates that one recording is a new recording derived from, based on, or made again from an earlier recording.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3b5b088190a58715779d2c46a6 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.