Triple
T37554154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molten Core |
E933653
|
entity |
| Predicate | statusInClassic |
P160687
|
FINISHED |
| Object | launch-tier raid |
—
|
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: launch-tier raid | Statement: [Molten Core, statusInClassic, launch-tier raid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInClassic Context triple: [Molten Core, statusInClassic, launch-tier raid]
-
A.
classicStatus
chosen
Indicates that an entity has been designated or recognized as a classic according to some standard or criteria.
-
B.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
C.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
D.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:17 p.m.