Triple
T37551082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trial of the Crusader |
E933590
|
entity |
| Predicate | bossCountedAsEncounter |
P64131
|
FINISHED |
| Object | Gormok the Impaler |
—
|
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: Gormok the Impaler | Statement: [Trial of the Crusader, bossCountedAsEncounter, Gormok the Impaler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossCountedAsEncounter Context triple: [Trial of the Crusader, bossCountedAsEncounter, Gormok the Impaler]
-
A.
hasBossFights
Indicates that something (such as a game, level, or scenario) includes one or more boss battles against especially powerful opponents.
-
B.
numberOfBosses
Indicates the count of distinct boss or supervisor entities associated with a given entity.
-
C.
roofBossesCount
Indicates the number of bosses (raised or protruding elements) present on a roof.
-
D.
notableBoss
chosen
Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
-
E.
hasNotableTribeAtEncounter
Indicates that, at the time of the encounter, the entity was associated with or identified as belonging to a notable tribe.
- 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_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. |
Created at: May 3, 2026, 4:17 p.m.