Triple
T28369603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oshima District, Kagoshima |
E718588
|
entity |
| Predicate | hasFormerVillage |
P54403
|
FINISHED |
| Object | Isen Village |
—
|
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: Isen Village | Statement: [Oshima District, Kagoshima, hasFormerVillage, Isen Village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerVillage Context triple: [Oshima District, Kagoshima, hasFormerVillage, Isen Village]
-
A.
hasFormerSettlement
chosen
Indicates that a location previously contained a settlement that no longer exists or is no longer inhabited.
-
B.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
C.
hasOldCity
Indicates that an entity possesses or contains an old or historic city as part of its domain or structure.
-
D.
isAncestralVillageOf
Indicates that one place is the original home or traditional village from which another person, family, or community traces its ancestry.
-
E.
hasHistoricVillageArea
Indicates that an entity includes or is associated with an area recognized as a historic village or traditional settlement zone.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 28, 2026, 12:58 a.m.