Triple
T37472456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanguine Depths |
E931186
|
entity |
| Predicate | hasMythicPlusAffixSynergy |
P188684
|
FINISHED |
| Object | Sanguine |
—
|
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: Sanguine | Statement: [Sanguine Depths, hasMythicPlusAffixSynergy, Sanguine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythicPlusAffixSynergy Context triple: [Sanguine Depths, hasMythicPlusAffixSynergy, Sanguine]
-
A.
hasMythicMotif
Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other entity.
-
B.
hasMythicMode
Indicates that an entity possesses or supports a special "mythic" difficulty or mode beyond standard levels.
-
C.
hasMythicTheme
Indicates that something embodies, references, or is characterized by a mythic or mythological theme.
-
D.
isMythicPrototypeOf
Indicates that one entity serves as the mythic or legendary archetype, model, or original form upon which the other entity is based or derived.
-
E.
hasMythicSuccessor
Indicates that one entity is followed or replaced by another entity in a legendary, mythological, or otherwise exalted succession.
- F. None of above. chosen
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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.