Triple
T37457215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casino Mage |
E930828
|
entity |
| Predicate | deckBuildingFocus |
P188337
|
FINISHED |
| Object | including many random-effect Mage cards |
—
|
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: including many random-effect Mage cards | Statement: [Casino Mage, deckBuildingFocus, including many random-effect Mage cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deckBuildingFocus Context triple: [Casino Mage, deckBuildingFocus, including many random-effect Mage cards]
-
A.
architecturalFocus
Indicates that something is the primary subject, theme, or area of emphasis within the domain of architecture.
-
B.
targetedBuilding
Indicates that an entity intentionally directed an attack or operation toward a specific building.
-
C.
featuresBuilding
Indicates that one entity includes or incorporates a building as a notable component or characteristic.
-
D.
collectingFocus
Indicates that an entity is directing attention or effort toward gathering or assembling items, information, or resources.
-
E.
seeksToBuild
Indicates an intention or effort by one entity to create, develop, or establish something.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.