Triple
T38589756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaelastrasz the Corrupt |
E932425
|
entity |
| Predicate | phaseOfFight |
P139049
|
FINISHED |
| Object | single-phase burn encounter |
—
|
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: single-phase burn encounter | Statement: [Vaelastrasz the Corrupt, phaseOfFight, single-phase burn encounter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseOfFight Context triple: [Vaelastrasz the Corrupt, phaseOfFight, single-phase burn encounter]
-
A.
warPhase
Indicates the specific stage or period within a war or armed conflict during which an event, action, or condition occurs.
-
B.
bossBattlePhase
chosen
Indicates the specific stage or phase within a boss battle that an entity is currently engaged in.
-
C.
movementPhase
Indicates the specific stage or step within a larger movement or motion process that an action or entity is currently in.
-
D.
commonRacePhase
Indicates that two or more race events share the same phase or stage within a larger racing sequence or structure.
-
E.
encounterPhases
Indicates the distinct stages or periods through which an encounter or interaction progresses.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.