Triple
T37460011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maexxna |
E930893
|
entity |
| Predicate | encounterPhase |
P139049
|
FINISHED |
| Object | pre-30% health phase |
—
|
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: pre-30% health phase | Statement: [Maexxna, encounterPhase, pre-30% health phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounterPhase Context triple: [Maexxna, encounterPhase, pre-30% health phase]
-
A.
engagementPhase
Indicates the specific stage or phase an ongoing interaction, project, or relationship is currently in within its overall lifecycle.
-
B.
commonRacePhase
Indicates that two or more race events share the same phase or stage within a larger racing sequence or structure.
-
C.
timeframeOfMainEncounter
Indicates the specific period or duration during which the primary encounter or main interaction between the entities takes place.
-
D.
bossBattlePhase
chosen
Indicates the specific stage or phase within a boss battle that an entity is currently engaged in.
-
E.
approachingPhase
Indicates that one entity is moving closer to another entity or target, entering a phase of decreasing distance or separation.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.