Triple
T11563646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molten Core |
E274200
|
entity |
| Predicate | levelRequirementOriginal |
P56693
|
FINISHED |
| Object | 60 |
—
|
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: 60 | Statement: [Molten Core, levelRequirementOriginal, 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelRequirementOriginal Context triple: [Molten Core, levelRequirementOriginal, 60]
-
A.
requiresSkillLevel
chosen
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
-
B.
definesRequirementLevel
Indicates that one entity specifies or assigns the degree or strictness of obligation required for another entity.
-
C.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
-
D.
establishedRequirement
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
E.
requiresSubjectsAtLevel
Indicates that an entity depends on other subjects being present or qualified at a specified level in order for a condition, action, or state to be valid or achievable.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd2016481909b33848af3d1d6c1 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.