Triple
T37460670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haunted Creeper |
E930907
|
entity |
| Predicate | costEfficiency |
P174638
|
FINISHED |
| Object | High for aggressive decks |
—
|
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: High for aggressive decks | Statement: [Haunted Creeper, costEfficiency, High for aggressive decks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costEfficiency Context triple: [Haunted Creeper, costEfficiency, High for aggressive decks]
-
A.
costOptimized
Indicates that an action, process, or solution is arranged or configured to minimize cost while maintaining required performance or constraints.
-
B.
efficiency
chosen
Indicates how effectively an entity converts inputs (such as time, energy, or resources) into desired outputs or results.
-
C.
economicCost
Indicates the financial burden, expense, or resource expenditure associated with an action, event, or relationship between entities.
-
D.
costImpact
Indicates the effect that one entity or action has on the cost associated with another entity or process.
-
E.
costModel
Indicates the pricing or cost-structure relationship applied to an entity, defining how its costs are calculated or charged.
- 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_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.