Triple
T37540863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echo (Hearthstone keyword) |
E933321
|
entity |
| Predicate | cardTypeApplicableTo |
P5430
|
FINISHED |
| Object | spell |
—
|
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: spell | Statement: [Echo (Hearthstone keyword), cardTypeApplicableTo, spell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardTypeApplicableTo Context triple: [Echo (Hearthstone keyword), cardTypeApplicableTo, spell]
-
A.
cardType
chosen
Indicates the classification or category assigned to a card within a given system or context.
-
B.
cardEligibility
Indicates whether an entity qualifies for or is allowed to receive a particular card under specified criteria.
-
C.
cardTypeAccess
Indicates that access or permissions are determined or constrained based on the type of card involved.
-
D.
compatibleICCardBrand
Indicates that one entity (such as a device or system) supports and can properly operate with IC cards of the specified brand.
-
E.
hasMatchCardType
Indicates that two or more items share the same card type or that an item is associated with a specific matching card type.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:17 p.m.