Triple
T37508167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phial of Serenity |
E932149
|
entity |
| Predicate | usableContent |
P103156
|
FINISHED |
| Object | Shadowlands zones |
—
|
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: Shadowlands zones | Statement: [Phial of Serenity, usableContent, Shadowlands zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usableContent Context triple: [Phial of Serenity, usableContent, Shadowlands zones]
-
A.
allowedContent
Indicates that certain content is permitted or acceptable within a given context, policy, or system.
-
B.
contentUsage
chosen
Indicates how a piece of content is intended to be used, accessed, or consumed within a given context or system.
-
C.
usableAs
Indicates that one entity can function in place of or serve the purpose of another entity.
-
D.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
E.
contentLicenseAllows
Indicates that a content license grants permission for a specified use or action involving the content.
- 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_69f76ec5268481909ea01c73aeeefd42 |
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. |
Created at: May 3, 2026, 4:17 p.m.