Triple
T37661628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eye of Ender |
E937729
|
entity |
| Predicate | usedToAccess |
P41137
|
FINISHED |
| Object | the End dimension |
—
|
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: the End dimension | Statement: [Eye of Ender, usedToAccess, the End dimension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToAccess Context triple: [Eye of Ender, usedToAccess, the End dimension]
-
A.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
B.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
C.
accessedThrough
chosen
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
D.
laterAccessedBy
Indicates that an entity is subsequently accessed or used by another entity at a later point in time.
-
E.
usedToAuthorize
Indicates that something serves as the basis or instrument for granting permission, approval, or official power to perform an action.
- 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_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.