Triple
T37461022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y’Shaarj, Rage Unbound |
E930915
|
entity |
| Predicate | deckBuildingLimit |
P187873
|
FINISHED |
| Object | 1 copy per deck |
—
|
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: 1 copy per deck | Statement: [Y’Shaarj, Rage Unbound, deckBuildingLimit, 1 copy per deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deckBuildingLimit Context triple: [Y’Shaarj, Rage Unbound, deckBuildingLimit, 1 copy per deck]
-
A.
deckbuildingConstraint
chosen
Indicates a rule or limitation that governs how components (such as cards or items) may be selected, combined, or included when constructing a deck or similar collection.
-
B.
teamLimitType
Indicates the rule or constraint that defines how many members or teams are allowed within a given context.
-
C.
definesLimitOf
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
-
D.
deckBuildingFocus
Indicates a primary emphasis on constructing and optimizing decks as a central mechanic or activity within a game or system.
-
E.
wicketLimit
Indicates a constraint or maximum allowable number of wickets (e.g., dismissals) within a specified context or period.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.