Triple
T11658820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ender Dragon |
E277072
|
entity |
| Predicate | unlocks |
P93413
|
FINISHED |
| Object | End exit portal |
—
|
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 exit portal | Statement: [Ender Dragon, unlocks, End exit portal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlocks Context triple: [Ender Dragon, unlocks, End exit portal]
-
A.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
B.
releaseObtainedBy
Indicates that a particular release results from, or is produced through, a specified obtaining or acquisition process.
-
C.
unlockBehavior
chosen
Indicates that one entity enables access to or activates the behavior, functionality, or state of another entity.
-
D.
locks
Indicates that one entity secures, fastens, or restricts access to another entity, typically preventing its use or opening without proper authorization or a key.
-
E.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.