Triple
T37554228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bindings of the Windseeker |
E933655
|
entity |
| Predicate | dropRestriction |
P188277
|
FINISHED |
| Object | classic 40-player raid |
—
|
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: classic 40-player raid | Statement: [Bindings of the Windseeker, dropRestriction, classic 40-player raid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dropRestriction Context triple: [Bindings of the Windseeker, dropRestriction, classic 40-player raid]
-
A.
dropPolicy
Indicates that one entity enforces a rule or configuration specifying under what conditions certain items, requests, or data are discarded or not processed.
-
B.
dropCondition
Indicates that an entity ceases to satisfy, or is no longer subject to, a specified condition or requirement.
-
C.
dropName
Indicates that one entity mentions or reveals the name of another entity, often to gain recognition, advantage, or association.
-
D.
drop
Indicates that an entity causes something to fall or be released from a higher position to a lower one.
-
E.
dropType
Indicates the manner or category of how something is dropped, released, or caused to fall.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.