Triple
T37555087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of the Chosen |
E933676
|
entity |
| Predicate | roleInMaldraxxus |
P203896
|
FINISHED |
| Object | military leadership |
—
|
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: military leadership | Statement: [House of the Chosen, roleInMaldraxxus, military leadership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMaldraxxus Context triple: [House of the Chosen, roleInMaldraxxus, military leadership]
-
A.
roleInBladeTrinity
Indicates that an entity participated in the movie "Blade: Trinity" in a specific role (such as actor, director, or crew position).
-
B.
roleInSpearOfDestiny
Indicates that an entity has a specific role or involvement in the context of the Spear of Destiny.
-
C.
roleInMalfunkshun
Indicates that an entity holds or held a specific role or position within the band Malfunkshun.
-
D.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
-
E.
roleInDarkReign
Indicates that an entity holds a specific role or participation in the "Dark Reign" event, storyline, or operation.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0245e917748190bf0a65db538aa66f |
completed | May 11, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_6a023f7cf7148190af5c2ea501511145 |
completed | May 11, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_6a0245e83d5c8190b3cf9a5ea17c5d9c |
completed | May 11, 2026, 9:11 p.m. |
Created at: May 3, 2026, 4:17 p.m.