Triple
T37507378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beastwarrens |
E932130
|
entity |
| Predicate | playerLimit |
P194927
|
FINISHED |
| Object | open world (no fixed group size) |
—
|
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: open world (no fixed group size) | Statement: [Beastwarrens, playerLimit, open world (no fixed group size)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerLimit Context triple: [Beastwarrens, playerLimit, open world (no fixed group size)]
-
A.
teamLimitType
Indicates the rule or constraint that defines how many members or teams are allowed within a given context.
-
B.
teamLimitPerGame
Indicates the maximum number of times a team is allowed to participate or be involved in a single game or match.
-
C.
maximumPlayerCount
Indicates the largest number of players that can participate at the same time in the related context or activity.
-
D.
playerCapacity
Indicates the maximum number of players that can simultaneously participate in or be accommodated by something (such as a game, session, or venue).
-
E.
teamLimitInRecentEditions
Indicates a constraint on the number of teams allowed to participate in the most recent editions of a competition or event.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
| PDg | Predicate description generation | batch_69fd8e5e9ca48190890a2caddc1f9f5c |
completed | May 8, 2026, 7:18 a.m. |
Created at: May 3, 2026, 4:17 p.m.