Triple
T38584784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadow Labyrinth |
E932321
|
entity |
| Predicate | heroicRequiresReputationWith |
P191450
|
FINISHED |
| Object | Lower City |
—
|
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: Lower City | Statement: [Shadow Labyrinth, heroicRequiresReputationWith, Lower City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroicRequiresReputationWith Context triple: [Shadow Labyrinth, heroicRequiresReputationWith, Lower City]
-
A.
heroicRequiresKey
Indicates that performing the heroic action or accessing the heroic mode is contingent on possessing a specific key.
-
B.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
C.
heroicStatus
Indicates that an entity possesses qualities or recognition associated with being a hero, such as bravery, selflessness, or notable heroic deeds.
-
D.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
E.
reputationInLore
Indicates how an entity is regarded or reputed within a fictional or narrative lore context.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.