Triple
T28668191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R'lyehian |
E725636
|
entity |
| Predicate | languageTypeInFiction |
P107786
|
FINISHED |
| Object | otherworldly language |
—
|
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: otherworldly language | Statement: [R'lyehian, languageTypeInFiction, otherworldly language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageTypeInFiction Context triple: [R'lyehian, languageTypeInFiction, otherworldly language]
-
A.
languageWithinFiction
Indicates that a language is used or exists within the context of a fictional work or fictional universe.
-
B.
fictionalType
Indicates that one entity is a fictional or imaginary type or category of the other entity.
-
C.
fictionalLanguage
chosen
Indicates a relationship where an entity uses, is expressed in, or is associated with a language that is invented or does not exist in reality.
-
D.
literaryLanguage
Indicates that an entity is expressed, written, or communicated using a particular literary or standardized written language.
-
E.
fictionalUniverseLanguage
Indicates that a language is used or exists within a particular fictional universe.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 28, 2026, 5:02 a.m.