Triple
T38589813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broodlord Lashlayer |
E932426
|
entity |
| Predicate | raidPreparation |
P2534
|
FINISHED |
| Object | requires trash clearing before pull |
—
|
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: requires trash clearing before pull | Statement: [Broodlord Lashlayer, raidPreparation, requires trash clearing before pull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidPreparation Context triple: [Broodlord Lashlayer, raidPreparation, requires trash clearing before pull]
-
A.
pitPreparation
Indicates the action or process of creating, arranging, or readying a pit or pit area for a subsequent use or event.
-
B.
preparesForRank
Indicates that one entity is used, undertaken, or designed to help another entity achieve or qualify for a particular rank or level.
-
C.
preparesFor
chosen
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
D.
preparedBefore
Indicates that one entity was prepared or made ready at an earlier time than another entity.
-
E.
preparedFor
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with another entity.
- 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.