Triple
T38478084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shores of Hell |
E915599
|
entity |
| Predicate | hasMapRange |
P204676
|
FINISHED |
| Object | E2M1–E2M9 |
—
|
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: E2M1–E2M9 | Statement: [The Shores of Hell, hasMapRange, E2M1–E2M9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapRange Context triple: [The Shores of Hell, hasMapRange, E2M1–E2M9]
-
A.
hasMapRegion
Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
-
B.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
C.
hasMapType
Indicates that one entity is associated with a specific type or category of map.
-
D.
hasMapBy
Indicates that one entity is represented, depicted, or detailed by a specific map associated with it.
-
E.
hasMapStructure
Indicates that one entity is organized or represented according to the structural layout or schema defined by another (map-like) entity.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:31 p.m.