Triple
T37470727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikanikos |
E931144
|
entity |
| Predicate | sanctum |
P8131
|
FINISHED |
| Object | Elysian Hold |
—
|
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: Elysian Hold | Statement: [Mikanikos, sanctum, Elysian Hold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctum Context triple: [Mikanikos, sanctum, Elysian Hold]
-
A.
sanctumContains
Indicates that one sanctum or sacred space physically or conceptually includes or holds another entity within its bounds.
-
B.
sacredTruce
Indicates a formally recognized period during which hostilities or conflicts are suspended, often for religious or ceremonial reasons.
-
C.
sacredTo
chosen
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
D.
principalSacrament
Indicates that one sacrament holds primary or highest importance in relation to another or within a given religious or ritual context.
-
E.
otherRelatedSanctums
Indicates that there exist additional sanctums that are related or connected to a given sanctum in some relevant way.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8e61d5a48190afc273af1fb54af9 |
completed | May 6, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0c53c08190b64291bac58cdb4c |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.