Triple
T27320418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitaiōjima |
E689476
|
entity |
| Predicate | formerAdministrativeName |
P171724
|
FINISHED |
| Object | Kita Iōjima |
—
|
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: Kita Iōjima | Statement: [Kitaiōjima, formerAdministrativeName, Kita Iōjima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerAdministrativeName Context triple: [Kitaiōjima, formerAdministrativeName, Kita Iōjima]
-
A.
formerNameOfRegion
chosen
Indicates that one name was previously used for a region that is now known by a different name.
-
B.
formerNameOfProvince
Indicates that one name was previously used as the official name of a province before being replaced by another name.
-
C.
formerNameOfDistrict
Indicates that one district previously had a different official name, which is the value linked by this predicate.
-
D.
formerAdministrativeTerritory
Indicates that one entity was previously an official administrative territory of another entity but no longer holds that status.
-
E.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 27, 2026, 11:32 a.m.