Triple
T37472269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halls of Atonement |
E931181
|
entity |
| Predicate | hasMythicPlusTimer |
P139545
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Halls of Atonement, hasMythicPlusTimer, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythicPlusTimer Context triple: [Halls of Atonement, hasMythicPlusTimer, true]
-
A.
hasMythicTimeframe
Indicates that the relationship associates something with a timeframe situated in mythic or legendary, rather than historical, time.
-
B.
hasMythicFounder
Indicates that an entity is traditionally believed to have been founded or established by a legendary or mythological figure rather than a historically verified person.
-
C.
hasMythicEvent
Indicates that an entity is associated with, involves, or features a significant mythic or legendary event.
-
D.
hasMythicMode
chosen
Indicates that an entity possesses or supports a special "mythic" difficulty or mode beyond standard levels.
-
E.
hasMythicMotif
Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other entity.
- 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_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.