Triple
T37463773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rush (Hearthstone keyword) |
E930983
|
entity |
| Predicate | introducedAsEvergreenKeyword |
P198303
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rush (Hearthstone keyword), introducedAsEvergreenKeyword, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsEvergreenKeyword Context triple: [Rush (Hearthstone keyword), introducedAsEvergreenKeyword, true]
-
A.
introducesKeyword
Indicates that one entity presents or brings a specific keyword into use or into a given context.
-
B.
introducedAsNameIn
Indicates that an entity is presented or referred to by a particular name within a specified context or source.
-
C.
termIntroducedBy
Indicates that a specific term was first presented, defined, or brought into use by a particular source or agent.
-
D.
settingIntroducedIn
Indicates the work, installment, or context in which a particular setting first appears or is established.
-
E.
introducedAsFirst
Indicates that one entity is presented or mentioned before any others in a given context or sequence.
- 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_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
| PDg | Predicate description generation | batch_69fed83a3b8c819092a3bd1ca9d9b38b |
completed | May 9, 2026, 6:46 a.m. |
Created at: May 3, 2026, 4:17 p.m.