Triple
T37540871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echo (Hearthstone keyword) |
E933321
|
entity |
| Predicate | zoneInteraction |
P187947
|
FINISHED |
| Object | Echo copies only exist in hand and are not added to the 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: Echo copies only exist in hand and are not added to the deck. | Statement: [Echo (Hearthstone keyword), zoneInteraction, Echo copies only exist in hand and are not added to the deck.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneInteraction Context triple: [Echo (Hearthstone keyword), zoneInteraction, Echo copies only exist in hand and are not added to the deck.]
-
A.
zoneBased
Indicates that the relationship or action is determined or constrained by specific geographic or logical zones.
-
B.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
C.
demilitarizedZonePolicedBy
Indicates that a demilitarized zone is monitored, controlled, or kept secure by a specified policing authority or force.
-
D.
zoneBehavior
chosen
Indicates how an entity is expected to act or be treated within a specific zone or area.
-
E.
zoneAdded
Indicates that a new zone has been created and incorporated into an existing system, area, or configuration.
- 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_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.