Triple
T31439504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogueport Inn |
E802028
|
entity |
| Predicate | locatedInGameWorld |
P190569
|
FINISHED |
| Object | Rogueport harbor town |
—
|
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: Rogueport harbor town | Statement: [Rogueport Inn, locatedInGameWorld, Rogueport harbor town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInGameWorld Context triple: [Rogueport Inn, locatedInGameWorld, Rogueport harbor town]
-
A.
isOnWorld
Indicates that one entity is located on, or exists upon the surface or within the domain of, a particular world or planet.
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
inGameLocationType
Indicates that an entity has a specific type or category of location within a game world (e.g., city, dungeon, region).
-
D.
inGameWorld
chosen
Indicates that an entity exists or is located within the context or boundaries of a particular game world.
-
E.
locatedOnTerrain
Indicates that one entity is physically situated on or atop a particular terrain surface.
- 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_6a018f9c7cf88190adc5daf3806f2077 |
completed | May 11, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_6a018ca4e0e481908091f0c1f8a4c31b |
completed | May 11, 2026, 8 a.m. |
Created at: April 30, 2026, 9:04 p.m.