Triple
T31439387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogueport Harbor |
E802024
|
entity |
| Predicate | regionInGameWorld |
P88332
|
FINISHED |
| Object | Rogueport region |
—
|
NE NERFINISHED |
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: Rogueport region | Statement: [Rogueport Harbor, regionInGameWorld, Rogueport region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionInGameWorld Context triple: [Rogueport Harbor, regionInGameWorld, Rogueport region]
-
A.
regionInGame
chosen
Indicates that a specific region or area exists within or is part of a particular game.
-
B.
inGameContinent
Indicates that something is located within or associated with a specific continent in the context of a game world.
-
C.
zoneNumberInGame
Indicates that an entity is associated with a specific numbered zone within a game.
-
D.
inGameWorld
Indicates that an entity exists or is located within the context or boundaries of a particular game world.
-
E.
regionPlayedFor
Indicates the geographic region or area that an entity (typically a person or team) has represented or played for.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 30, 2026, 9:04 p.m.