Triple
T38110630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galakrond, the Wretched |
E951643
|
entity |
| Predicate | hasDeckbuildingLimit |
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: [Galakrond, the Wretched, hasDeckbuildingLimit, 1 copy per deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeckbuildingLimit Context triple: [Galakrond, the Wretched, hasDeckbuildingLimit, 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.
hasDeckControl
Indicates that one entity has operational authority or management control over a deck or deck-like area associated with another entity.
-
C.
playerLimit
Indicates the maximum number of players allowed to participate in a given game, session, or activity.
-
D.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
hasMultipleDecks
Indicates that an entity possesses more than one deck or layered level within its structure.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 3, 2026, 4:21 p.m.