Triple
T10090431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rexford Bedlo |
E215327
|
entity |
| Predicate | toneOfWork |
P7344
|
FINISHED |
| Object | parody of gothic horror |
—
|
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: parody of gothic horror | Statement: [Rexford Bedlo, toneOfWork, parody of gothic horror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toneOfWork Context triple: [Rexford Bedlo, toneOfWork, parody of gothic horror]
-
A.
tone
chosen
Indicates the characteristic attitude or emotional quality expressed in how something is communicated or presented.
-
B.
tonal
Indicates that one entity has a tone, pitch pattern, or tonal quality in relation to another (such as a language, sound, or musical element).
-
C.
timbrality
Indicates the relationship between sounds or musical elements in terms of their tone color or quality, distinguishing how they differ or interact based on timbre.
-
D.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
E.
contributesToTone
Indicates that one entity plays a role in shaping, influencing, or determining the overall tone or mood of another entity.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd05960008190baecb8e4c9f2461f |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.