Triple
T35105294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Key to All Mythologies |
E1013134
|
entity |
| Predicate | languageOfCompositionInFiction |
P17914
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [The Key to All Mythologies, languageOfCompositionInFiction, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCompositionInFiction Context triple: [The Key to All Mythologies, languageOfCompositionInFiction, English]
-
A.
languageOfWritings
chosen
Indicates that a specified language is the one in which certain writings or written works are composed.
-
B.
languageWrittenAbout
Indicates that something is written about or concerning a particular language.
-
C.
literaryLanguage
Indicates that an entity is expressed, written, or communicated using a particular literary or standardized written language.
-
D.
languageWithinFiction
Indicates that a language is used or exists within the context of a fictional work or fictional universe.
-
E.
languageOfFictionalUniverse
Indicates the language used or spoken within a fictional universe or setting.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00ae638fcc819096537b2c21366161 |
completed | May 10, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_6a00ae0551988190bcb3564ed9af2847 |
completed | May 10, 2026, 4:10 p.m. |
Created at: May 3, 2026, 4:01 p.m.