Triple
T37661588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End Barrens |
E937728
|
entity |
| Predicate | hasMobSpawn |
P100833
|
FINISHED |
| Object | enderman |
—
|
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: enderman | Statement: [End Barrens, hasMobSpawn, enderman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMobSpawn Context triple: [End Barrens, hasMobSpawn, enderman]
-
A.
spawnsHostileMobs
chosen
Indicates that the subject causes or triggers the appearance of enemy or hostile creatures.
-
B.
hasMob
Indicates that an entity possesses, controls, or is associated with a particular mob or group of mobile agents.
-
C.
canSpawnWith
Indicates that one entity is able to appear, be created, or originate in conjunction with another entity under the same conditions or context.
-
D.
hasCreature
Indicates that one entity possesses, contains, or is associated with a particular creature.
-
E.
spawns
Indicates that one entity generates, creates, or gives rise to another entity, often as an origin or source.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:18 p.m.