Triple
T16624900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krimzon Guard fortress |
E403919
|
entity |
| Predicate | accessMethodInGame |
P5872
|
FINISHED |
| Object | story‑driven missions |
—
|
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: story‑driven missions | Statement: [Krimzon Guard fortress, accessMethodInGame, story‑driven missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessMethodInGame Context triple: [Krimzon Guard fortress, accessMethodInGame, story‑driven missions]
-
A.
accessMethod
chosen
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
B.
accessMission
Indicates that an entity is permitted to enter, use, or interact with a specific mission or mission-related resources.
-
C.
accessesPass
Indicates that one entity uses or is granted a pass (such as a credential, ticket, or authorization token) to gain entry to or make use of another entity.
-
D.
accessFeature
Indicates that one entity is permitted to use or interact with a specific feature or capability of another entity.
-
E.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37551cd888190becc21deba87980d |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.