Triple
T36961360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tome of Power |
E914314
|
entity |
| Predicate | loreContext |
P2919
|
FINISHED |
| Object | magical tome |
—
|
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: magical tome | Statement: [Tome of Power, loreContext, magical tome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loreContext Context triple: [Tome of Power, loreContext, magical tome]
-
A.
loreType
Indicates the category or kind of lore that characterizes or classifies a given entity or subject.
-
B.
loreConnection
Indicates a relationship where two entities are linked through shared story, background, or world-building context within a fictional or narrative universe.
-
C.
loreFunction
Indicates that something serves a narrative or world-building role within a fictional or informational context.
-
D.
speciesContext
Indicates the biological or taxonomic context in which a species is situated or interpreted (e.g., its classification, environment, or relevant ecological setting).
-
E.
contextOf
chosen
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.