Triple
T35355478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hachijō-jima |
E1021310
|
entity |
| Predicate | usedAsExileLocationBy |
P10493
|
FINISHED |
| Object | Tokugawa shogunate |
—
|
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: Tokugawa shogunate | Statement: [Hachijō-jima, usedAsExileLocationBy, Tokugawa shogunate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsExileLocationBy Context triple: [Hachijō-jima, usedAsExileLocationBy, Tokugawa shogunate]
-
A.
exileLocation
chosen
Indicates the place or destination to which an entity is sent or kept in exile.
-
B.
usedInExile
Indicates that something (such as a method, name, or identity) is employed or applied while an entity is in a state of exile.
-
C.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
D.
outfallLocation
Indicates the geographic place where a discharge, such as wastewater or runoff, is released into the environment.
-
E.
servesAsTerritorialBaseFor
Indicates that a place or area functions as the primary territorial base or stronghold from which an entity operates or exerts influence.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 3, 2026, 4:03 p.m.