Triple
T37540880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echo (Hearthstone keyword) |
E933321
|
entity |
| Predicate | standardFormatStatus |
P116480
|
FINISHED |
| Object | rotated out of Standard |
—
|
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: rotated out of Standard | Statement: [Echo (Hearthstone keyword), standardFormatStatus, rotated out of Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardFormatStatus Context triple: [Echo (Hearthstone keyword), standardFormatStatus, rotated out of Standard]
-
A.
formatStatus
chosen
Indicates the current state or condition of a particular format, such as whether it is valid, active, or in use.
-
B.
standardForReporting
Indicates that something is used as the accepted or prescribed basis, format, or reference for reporting information or results.
-
C.
statusInText
Indicates that the text explicitly states or conveys the status or condition of an entity.
-
D.
standardCreated
Indicates that an entity is responsible for the creation or establishment of a particular standard.
-
E.
standardizationStatus
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
- 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_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 3, 2026, 4:17 p.m.