Triple
T31439376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogueport Harbor |
E802024
|
entity |
| Predicate | gameChapterRelevance |
P171875
|
FINISHED |
| Object | Chapter 5 travel point |
—
|
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: Chapter 5 travel point | Statement: [Rogueport Harbor, gameChapterRelevance, Chapter 5 travel point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameChapterRelevance Context triple: [Rogueport Harbor, gameChapterRelevance, Chapter 5 travel point]
-
A.
gameChapter
Indicates that one entity is a chapter, level, or segment that forms part of the progression or structure of a game.
-
B.
basedOnChapter
Indicates that something (such as a work, section, or element) is derived from, adapted from, or primarily informed by a specific chapter.
-
C.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by another entity.
-
D.
chapterMentioned
Indicates that a specific chapter is referenced or cited within a given context or source.
-
E.
rankWithinChapter
Indicates the relative ordering or position of an item among other items within the same chapter.
- F. None of above. chosen
Provenance (4 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 9:04 p.m.