Triple
T36958705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spear of Destiny |
E914252
|
entity |
| Predicate | holyRelic |
P50090
|
FINISHED |
| Object | Spear of Destiny |
—
|
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: Spear of Destiny | Statement: [Spear of Destiny, holyRelic, Spear of Destiny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holyRelic Context triple: [Spear of Destiny, holyRelic, Spear of Destiny]
-
A.
holyRelicDisplayedOn
Indicates that a sacred or revered religious object is being publicly shown or exhibited on a particular surface, structure, or location.
-
B.
relicsAssociatedWith
Indicates a relationship where certain relics are connected or linked to a particular entity, context, or subject (such as a person, place, event, or tradition).
-
C.
notableRelic
chosen
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
D.
relicDiscovery
Indicates the event or relationship in which an entity finds or uncovers a relic.
-
E.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
- 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:13 p.m.