Triple
T38584785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadow Labyrinth |
E932321
|
entity |
| Predicate | heroicReputationRequirement |
P191450
|
FINISHED |
| Object | Honored |
—
|
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: Honored | Statement: [Shadow Labyrinth, heroicReputationRequirement, Honored]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroicReputationRequirement Context triple: [Shadow Labyrinth, heroicReputationRequirement, Honored]
-
A.
heroicRequiresReputationWith
chosen
Indicates that achieving or performing a heroic-level action depends on having a sufficient reputation or standing with a specified party or group.
-
B.
heroicRequiresKey
Indicates that performing the heroic action or accessing the heroic mode is contingent on possessing a specific key.
-
C.
nobleRankRequired
Indicates that a certain minimum noble rank or title is required for the related action, status, or relationship to apply.
-
D.
heroicStatus
Indicates that an entity possesses qualities or recognition associated with being a hero, such as bravery, selflessness, or notable heroic deeds.
-
E.
heroicLevel
Indicates the degree or extent to which an entity exhibits heroism or heroic qualities.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:32 p.m.