Triple
T28895396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-102 Gamma |
E732821
|
entity |
| Predicate | hasBossBattleWith |
P86453
|
FINISHED |
| Object | E-101 Beta |
—
|
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: E-101 Beta | Statement: [E-102 Gamma, hasBossBattleWith, E-101 Beta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBossBattleWith Context triple: [E-102 Gamma, hasBossBattleWith, E-101 Beta]
-
A.
hasBossFights
chosen
Indicates that something (such as a game, level, or scenario) includes one or more boss battles against especially powerful opponents.
-
B.
stageBossOf
Indicates that one entity serves as the primary boss or main adversary encountered in a particular stage, level, or area associated with another entity.
-
C.
hasBattleScenes
Indicates that an entity (such as a work of fiction or media) contains scenes depicting battles or combat.
-
D.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or entity.
-
E.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 7:58 a.m.