Triple
T37661564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Small End Islands |
E937727
|
entity |
| Predicate | playerAccessMethod |
P5872
|
FINISHED |
| Object | End Gateway from main End island |
—
|
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 Gateway from main End island | Statement: [Small End Islands, playerAccessMethod, End Gateway from main End island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerAccessMethod Context triple: [Small End Islands, playerAccessMethod, End Gateway from main End island]
-
A.
accessMethod
chosen
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
B.
hasAccessMethod
Indicates that one entity uses or is associated with a particular method or mechanism for accessing another entity or resource.
-
C.
playbackAccess
Indicates that one entity is permitted to play back or view media content controlled or owned by another entity.
-
D.
typeOfAccess
Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
-
E.
canAccedeTo
Indicates that one entity has the ability, permission, or right to gain access to or enter into another entity, resource, or state.
- 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_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:18 p.m.