Triple
T37551367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahn'kahet: The Old Kingdom |
E933596
|
entity |
| Predicate | heroicLockout |
P188723
|
FINISHED |
| Object | daily |
—
|
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: daily | Statement: [Ahn'kahet: The Old Kingdom, heroicLockout, daily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroicLockout Context triple: [Ahn'kahet: The Old Kingdom, heroicLockout, daily]
-
A.
heroicRequiresKey
Indicates that performing the heroic action or accessing the heroic mode is contingent on possessing a specific key.
-
B.
heroicStatus
Indicates that an entity possesses qualities or recognition associated with being a hero, such as bravery, selflessness, or notable heroic deeds.
-
C.
heroicAction
Indicates that an entity performs a brave, selfless, or morally admirable action, often involving risk or sacrifice for the benefit of others.
-
D.
nativeHero
Indicates that an entity is regarded as a heroic figure originating from or strongly associated with a particular place or community.
-
E.
heroPerformsFor
Indicates that a hero carries out an action or performance for the benefit, entertainment, or service of another entity.
- F. None of above. chosen
Provenance (4 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.