Triple
T37540881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echo (Hearthstone keyword) |
E933321
|
entity |
| Predicate | formatAvailability |
P116480
|
FINISHED |
| Object | available in Wild format |
—
|
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: available in Wild format | Statement: [Echo (Hearthstone keyword), formatAvailability, available in Wild format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatAvailability Context triple: [Echo (Hearthstone keyword), formatAvailability, available in Wild format]
-
A.
formatStatus
chosen
Indicates the current state or condition of a particular format, such as whether it is valid, active, or in use.
-
B.
modernAvailability
Indicates that something is currently obtainable, accessible, or in use in the modern or present-day context.
-
C.
packageAvailability
Indicates whether a particular package is currently available for use, access, or distribution.
-
D.
availabilityModel
Indicates how and under what conditions an entity is available for use, access, or interaction.
-
E.
initialAvailability
Indicates the starting level or state of availability of an entity before any changes or updates occur.
- 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_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:17 p.m.