Triple
T37539164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpentshrine Cavern |
E933281
|
entity |
| Predicate | raidFormat |
P188707
|
FINISHED |
| Object | single-lockout |
—
|
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-lockout | Statement: [Serpentshrine Cavern, raidFormat, single-lockout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidFormat Context triple: [Serpentshrine Cavern, raidFormat, single-lockout]
-
A.
raidPosition
Indicates the spatial location or coordinates where a raid event takes place or is intended to occur.
-
B.
raid
Indicates a sudden, targeted attack or incursion by one party into another’s domain, typically to seize assets, gather information, or cause disruption.
-
C.
raidSize
Indicates the number of participants or units involved in a single raid event.
-
D.
raidInstance
Indicates that an entity participates in or is associated with a specific raid instance, typically representing a particular occurrence or session of a raid event.
-
E.
raidOrigin
Indicates the source location, group, or entity from which a raid is initiated or originates.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.