Triple
T20983416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shrine of Secrets |
E516825
|
entity |
| Predicate | hasUIAccessPoint |
P81316
|
FINISHED |
| Object | in-game store menu |
—
|
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: in-game store menu | Statement: [Shrine of Secrets, hasUIAccessPoint, in-game store menu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUIAccessPoint Context triple: [Shrine of Secrets, hasUIAccessPoint, in-game store menu]
-
A.
hasAccessPointFrom
chosen
Indicates that an entity can be reached or entered from a specific access point.
-
B.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
C.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
D.
hasAccessMethod
Indicates that one entity uses or is associated with a particular method or mechanism for accessing another entity or resource.
-
E.
hasAccessibleAccess
Indicates that an entity provides a form of access that is usable and reachable under defined accessibility conditions or standards.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe1474c8190912b90da0973f99f |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.