Triple
T37539086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azuremyst Isle |
E933279
|
entity |
| Predicate | startingExperience |
P89272
|
FINISHED |
| Object | new player tutorial content |
—
|
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: new player tutorial content | Statement: [Azuremyst Isle, startingExperience, new player tutorial content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingExperience Context triple: [Azuremyst Isle, startingExperience, new player tutorial content]
-
A.
settingOfExperience
Indicates that a particular context, environment, or situation serves as the backdrop or circumstances in which an experience occurs.
-
B.
typicalExperienceLevel
Indicates the usual or most common level of experience associated with an entity in a given context.
-
C.
primaryExperience
Indicates that one entity is the main or most significant experience associated with another entity, as opposed to secondary or supporting experiences.
-
D.
commandExperience
Indicates that an entity has experience or a track record in holding command or leadership roles over others.
-
E.
providesExperienceOf
chosen
Indicates that one entity enables or delivers the experience of another entity to someone or something.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0120f070b081909b6d1a3d8ee6b80e |
completed | May 11, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_6a01209da37481909683e38f264b15ef |
completed | May 11, 2026, 12:19 a.m. |
Created at: May 3, 2026, 4:17 p.m.