Triple
T37515618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echoes of the Atlas |
E932625
|
entity |
| Predicate | introducedContentForGame |
P192473
|
FINISHED |
| Object | Path of Exile endgame |
—
|
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: Path of Exile endgame | Statement: [Echoes of the Atlas, introducedContentForGame, Path of Exile endgame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedContentForGame Context triple: [Echoes of the Atlas, introducedContentForGame, Path of Exile endgame]
-
A.
hasGameContent
Indicates that an entity includes, provides, or is associated with game-related material or features.
-
B.
introducedToGame
Indicates that one entity caused or facilitated another entity’s initial exposure or introduction to a particular game.
-
C.
playableContentIntroducedIn
chosen
Indicates that a piece of playable content was first introduced or made available in a specific release, version, or installment.
-
D.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
E.
introducedGameMode
Indicates that an entity caused a particular game mode to be created, revealed, or made available for use.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 3, 2026, 4:17 p.m.