Triple
T37459241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fel Reaver |
E930875
|
entity |
| Predicate | hasDeckbuildingRestriction |
P187873
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Fel Reaver, hasDeckbuildingRestriction, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeckbuildingRestriction Context triple: [Fel Reaver, hasDeckbuildingRestriction, false]
-
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.
hasDeckType
Indicates that an entity possesses or is associated with a specific type or category of deck.
-
C.
hasPartyDeck
Indicates that something includes or is equipped with a designated deck or area intended for parties or social gatherings.
-
D.
canBePlayedWithPhysicalCards
Indicates that the game or activity is playable using tangible, real-world physical cards rather than (or in addition to) digital or virtual formats.
-
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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
Created at: May 3, 2026, 4:17 p.m.