Triple
T37551069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trial of the Crusader |
E933590
|
entity |
| Predicate | hasHeroicToggle |
P191249
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Trial of the Crusader, hasHeroicToggle, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroicToggle Context triple: [Trial of the Crusader, hasHeroicToggle, yes]
-
A.
isHeroicVariantAvailable
chosen
Indicates whether a special or enhanced "heroic" version of something is currently obtainable or enabled.
-
B.
hasHeroicResponder
Indicates that an entity is associated with or supported by another entity that performs a heroic or emergency response action on its behalf.
-
C.
hasHeroicTheme
Indicates that something (such as a work, scene, or motif) embodies or prominently features a heroic theme or quality.
-
D.
hasHeroicFortress
Indicates that an entity possesses or is associated with a fortress characterized by heroic qualities, status, or significance.
-
E.
canUseHero
Indicates that an entity is permitted or able to use a specified hero character.
- 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_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:17 p.m.