Triple
T37513707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Kurast |
E932576
|
entity |
| Predicate | dropTableCharacteristic |
P188192
|
FINISHED |
| Object | Super chests use special drop patterns |
—
|
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: Super chests use special drop patterns | Statement: [Lower Kurast, dropTableCharacteristic, Super chests use special drop patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dropTableCharacteristic Context triple: [Lower Kurast, dropTableCharacteristic, Super chests use special drop patterns]
-
A.
dropName
Indicates that one entity mentions or reveals the name of another entity, often to gain recognition, advantage, or association.
-
B.
removedCharacter
Indicates that a character was taken out or deleted from a text, sequence, or collection.
-
C.
dropElement
Indicates that an element is removed or discarded from a collection, sequence, or structure.
-
D.
dismissesCharacter
Indicates that one character rejects, disbelieves, or disregards another character, often minimizing their importance, ideas, or concerns.
-
E.
dropCondition
Indicates that an entity ceases to satisfy, or is no longer subject to, a specified condition or requirement.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
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. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.