Triple
T37783379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enderlings |
E941886
|
entity |
| Predicate | appearsInBiome |
P41820
|
FINISHED |
| Object | End dimension levels |
—
|
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: End dimension levels | Statement: [Enderlings, appearsInBiome, End dimension levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInBiome Context triple: [Enderlings, appearsInBiome, End dimension levels]
-
A.
isLocatedInBiome
Indicates that one entity is situated within or belongs to the environmental region or biome represented by another entity.
-
B.
biomeIncludes
chosen
Indicates that a biome contains or encompasses a particular entity, such as a species, habitat, or environmental feature, as part of its composition.
-
C.
hasSecondaryBiome
Indicates that an entity is associated with an additional, subordinate biome type beyond its primary biome.
-
D.
addsBiome
Indicates that one entity introduces or associates a new biome with another entity.
-
E.
cannotGenerateInBiome
Indicates that an entity or object is unable to be created, spawned, or produced within a specified biome.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:19 p.m.