Triple
T5585154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dark Eyes of London |
E146736
|
entity |
| Predicate | hasMysteryElements |
P21752
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Dark Eyes of London, hasMysteryElements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMysteryElements Context triple: [The Dark Eyes of London, hasMysteryElements, yes]
-
A.
hasMystery
chosen
Indicates that one entity possesses, contains, or is associated with something unknown, secret, or unexplained in relation to another entity.
-
B.
hasMysterySet
Indicates that an entity possesses or includes a collection or configuration whose nature or details are unknown or intentionally concealed.
-
C.
hasEnigmaticCharacter
Indicates that something possesses a mysterious, puzzling, or difficult-to-interpret quality or nature.
-
D.
hasMysteryCult
Indicates that an entity is associated with, participates in, or possesses a mystery cult, typically involving secret or esoteric religious practices.
-
E.
hasMythicMotif
Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02085d0e48190b8d185fe7f3d8579 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.