Triple
T37705136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungering Destroyer |
E939177
|
entity |
| Predicate | playerLimitContext |
P183407
|
FINISHED |
| Object | raid group only |
—
|
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: raid group only | Statement: [Hungering Destroyer, playerLimitContext, raid group only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerLimitContext Context triple: [Hungering Destroyer, playerLimitContext, raid group only]
-
A.
playerLimit
Indicates the maximum number of players allowed to participate in a given game, session, or activity.
-
B.
teamLimitType
chosen
Indicates the rule or constraint that defines how many members or teams are allowed within a given context.
-
C.
playerCapacity
Indicates the maximum number of players that can simultaneously participate in or be accommodated by something (such as a game, session, or venue).
-
D.
teamLimitPerGame
Indicates the maximum number of times a team is allowed to participate or be involved in a single game or match.
-
E.
maximumPlayerCount
Indicates the largest number of players that can participate at the same time in the related context or activity.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:18 p.m.