Triple
T35012150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auri-El |
E1009960
|
entity |
| Predicate | inGameLoreSource |
P183159
|
FINISHED |
| Object | The Monomyth |
—
|
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: The Monomyth | Statement: [Auri-El, inGameLoreSource, The Monomyth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGameLoreSource Context triple: [Auri-El, inGameLoreSource, The Monomyth]
-
A.
inGameZone
Indicates that an entity is located within a defined game zone or area of the game world.
-
B.
materialInLore
Indicates that a material is referenced, described, or plays a role within a body of lore or fictional/worldbuilding context.
-
C.
inGameName
Indicates that one entity is the name used by another entity within a specific game context.
-
D.
originGame
Indicates the game from which an entity, such as a character, item, or concept, originally comes.
-
E.
mentionedInGame
Indicates that an entity is referenced or cited within the content or dialogue of a game.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: May 3, 2026, 4:01 p.m.