Triple
T37664276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Prismarine |
E937785
|
entity |
| Predicate | dimensionAvailability |
P189524
|
FINISHED |
| Object | Overworld |
—
|
NE NERFINISHED |
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: Overworld | Statement: [Dark Prismarine, dimensionAvailability, Overworld]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dimensionAvailability Context triple: [Dark Prismarine, dimensionAvailability, Overworld]
-
A.
dimensionVariant
Indicates a relationship where one entity is a variant or alternative version of another with respect to certain dimensions or configurable attributes.
-
B.
dimensionStatus
Indicates the current state or condition of a given dimension (such as whether it is active, valid, complete, or in a particular lifecycle phase).
-
C.
dimensionType
Indicates the specific kind or category of dimension that characterizes how something is measured or structured.
-
D.
dimensionStatement
Indicates that a statement specifies the measured size, extent, or dimensional properties of an entity or relationship.
-
E.
dimensionCharacteristic
Indicates that one entity specifies or describes a dimensional property or measurement characteristic of another entity.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:18 p.m.