Triple
T37551078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trial of the Crusader |
E933590
|
entity |
| Predicate | supportsHardModeMechanic |
P199535
|
FINISHED |
| Object | Tribute run attempt counter |
—
|
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: Tribute run attempt counter | Statement: [Trial of the Crusader, supportsHardModeMechanic, Tribute run attempt counter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHardModeMechanic Context triple: [Trial of the Crusader, supportsHardModeMechanic, Tribute run attempt counter]
-
A.
hasChallengeMode
chosen
Indicates that an entity offers or is associated with a special, typically more difficult, challenge-oriented mode or setting.
-
B.
hasDifficultySetting
Indicates that an entity provides or is associated with a configurable level of difficulty.
-
C.
hasChallengeModeRewards
Indicates that an entity provides or is associated with rewards specifically granted for completing a challenge mode.
-
D.
impliesHardness
Indicates that one entity suggests, entails, or leads to the conclusion that another entity possesses hardness.
-
E.
supportsGameStyle
Indicates that one entity is compatible with or able to accommodate a particular game style or mode of play.
- 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.