Triple
T37874370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warbands (Diablo Immortal) |
E944680
|
entity |
| Predicate | groupSizeLimit |
P21198
|
FINISHED |
| Object | 8 players |
—
|
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: 8 players | Statement: [Warbands (Diablo Immortal), groupSizeLimit, 8 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupSizeLimit Context triple: [Warbands (Diablo Immortal), groupSizeLimit, 8 players]
-
A.
hasMaximumNumberOfMembers
chosen
Indicates that there is an upper limit on how many members can be associated with a given entity.
-
B.
groupSizePolicy
Indicates the rules or constraints governing how many entities can be included together in a single group.
-
C.
teamLimitType
Indicates the rule or constraint that defines how many members or teams are allowed within a given context.
-
D.
sizeOfGroup
Indicates the number of individuals or elements that make up a particular group.
-
E.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.