Triple
T37539152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpentshrine Cavern |
E933281
|
entity |
| Predicate | tierSet |
P100153
|
FINISHED |
| Object | Tier 5 |
—
|
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: Tier 5 | Statement: [Serpentshrine Cavern, tierSet, Tier 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierSet Context triple: [Serpentshrine Cavern, tierSet, Tier 5]
-
A.
tierCount
Indicates the number of distinct levels, ranks, or layers associated with an entity in a hierarchical or tiered structure.
-
B.
tierType
Indicates the classification level or rank assigned to an entity within a multi-level or hierarchical system.
-
C.
tierSetAssociation
chosen
Indicates an association that links an entity to a specific tier or tier set within a tiered structure or classification.
-
D.
tierConfiguration
Indicates how entities are organized or assigned into different levels or tiers according to a defined configuration or scheme.
-
E.
tierInNorthAmericanSystem
Indicates that an entity occupies a specified competitive or organizational level within the North American system for that domain (e.g., sports leagues, education, or other structured hierarchies).
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.