Triple
T38590045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neltharion's Tear |
E932431
|
entity |
| Predicate | canBeUsedInPvP |
P188270
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Neltharion's Tear, canBeUsedInPvP, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedInPvP Context triple: [Neltharion's Tear, canBeUsedInPvP, Yes]
-
A.
hasPvPArea
Indicates that a location or zone is designated for player-versus-player (PvP) interactions or combat.
-
B.
canAppearInArena
Indicates that an entity is eligible or allowed to participate or be present in an arena context.
-
C.
hasPvEContent
Indicates that something includes or provides player-versus-environment (PvE) gameplay content.
-
D.
hasPvPObjective
Indicates that an entity includes or is associated with a player-versus-player (PvP) objective or goal.
-
E.
pvpStatus
chosen
Indicates whether an entity is currently able or allowed to engage in player-versus-player (PvP) combat with other entities.
- 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_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:32 p.m.