Triple
T32904957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brichester Mythos |
E841709
|
entity |
| Predicate | hasFictionalEntity |
P15645
|
FINISHED |
| Object | Glaaki |
—
|
NE NERFINISHED |
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: Glaaki | Statement: [Brichester Mythos, hasFictionalEntity, Glaaki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalEntity Context triple: [Brichester Mythos, hasFictionalEntity, Glaaki]
-
A.
fictionalEntityIn
Indicates that a fictional entity appears in, is set within, or is part of the context of another work, setting, or universe.
-
B.
hasFictionalUniverseElement
chosen
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
C.
isFictionalPersonFrom
Indicates that a fictional person originates from or is associated with a particular place or source.
-
D.
hasFictionalLeadCharacter
Indicates that a creative work features a particular fictional character as its main or leading protagonist.
-
E.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: May 1, 2026, 1:19 a.m.