Triple
T37661640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eye of Ender |
E937729
|
entity |
| Predicate | requiredPerEndPortalFrame |
P107463
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Eye of Ender, requiredPerEndPortalFrame, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredPerEndPortalFrame Context triple: [Eye of Ender, requiredPerEndPortalFrame, 1]
-
A.
requiresPortalOfPower
Indicates that performing this action or relationship is only possible through or by using a specific portal of power.
-
B.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
C.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving another entity.
-
D.
hasPortal
Indicates that one entity possesses or provides access to a portal connecting to another location or entity.
-
E.
numberOfPortals
chosen
Indicates the quantity of portals associated with or contained by a given entity.
- 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_6a007ef69f5c8190be6fb89e918d30fa |
completed | May 10, 2026, 12:49 p.m. |
| PD | Predicate disambiguation | batch_6a007e4060448190ad7420b07c1fe219 |
completed | May 10, 2026, 12:46 p.m. |
Created at: May 3, 2026, 4:18 p.m.