Triple
T37461345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blood of The Ancient One |
E930923
|
entity |
| Predicate | flavorAssociation |
P188349
|
FINISHED |
| Object | Eldritch 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: Eldritch horror | Statement: [Blood of The Ancient One, flavorAssociation, Eldritch horror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flavorAssociation Context triple: [Blood of The Ancient One, flavorAssociation, Eldritch horror]
-
A.
hasFlavorAssociation
chosen
Indicates a relationship where one entity is conceptually or perceptually linked to a particular flavor or taste profile.
-
B.
flavorRole
Indicates a relationship where one entity serves a specific flavor-related function or contribution within the context of another entity (e.g., a component providing or modifying taste).
-
C.
flavorOrigin
Indicates the source or provenance from which a particular flavor or taste characteristic is derived.
-
D.
typicalFlavor
Indicates that something characteristically has or is associated with a particular flavor.
-
E.
isFlavored
Indicates that one entity imparts a particular taste or flavor characteristic to 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.