Triple
T37553305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Razor Hill Outskirts |
E933637
|
entity |
| Predicate | pvpStatus |
P188270
|
FINISHED |
| Object | contested only on PvP realms |
—
|
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: contested only on PvP realms | Statement: [Razor Hill Outskirts, pvpStatus, contested only on PvP realms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pvpStatus Context triple: [Razor Hill Outskirts, pvpStatus, contested only on PvP realms]
-
A.
playerStatus
Indicates the current state or condition of a player within a game or system, such as their activity, health, or participation status.
-
B.
POWStatus
Indicates that one entity is or has been held as a prisoner of war in relation to another entity or conflict.
-
C.
inGameStatus
Indicates the current state or condition of an entity within the context of a game (e.g., active, paused, eliminated).
-
D.
participantStatus
Indicates the role, condition, or level of involvement that a participant has within a specific event, process, or relationship.
-
E.
PVTGStatusState
Indicates the current status or condition of a private (PVTG) entity within a defined process or lifecycle.
- 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.