Triple
T36961250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethereal Crossbow |
E914311
|
entity |
| Predicate | loreAttribute |
P167556
|
FINISHED |
| Object | mystical origin |
—
|
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: mystical origin | Statement: [Ethereal Crossbow, loreAttribute, mystical origin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loreAttribute Context triple: [Ethereal Crossbow, loreAttribute, mystical origin]
-
A.
loreTrait
chosen
Indicates that an entity possesses a specific lore-related characteristic or attribute within a fictional or narrative context.
-
B.
coreAttribute
Indicates that one attribute is a fundamental, defining, or essential property of another entity.
-
C.
mythicAttribute
Indicates that one entity possesses or is characterized by a legendary, mythical, or folklore-based quality, power, or status in relation to another.
-
D.
creativeAttribute
Indicates that one entity possesses or is characterized by a creative quality, trait, or property in relation to another.
-
E.
loreRole
Indicates the specific narrative or canonical function an entity fulfills within a fictional or mythological lore.
- 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.