Triple
T35352297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miyakejima |
E1020916
|
entity |
| Predicate | resettlementAllowed |
P183051
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Miyakejima, resettlementAllowed, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resettlementAllowed Context triple: [Miyakejima, resettlementAllowed, 2005]
-
A.
resettlementStatus
Indicates the current stage or condition of an entity’s relocation or re-establishment process in a new place.
-
B.
hasResettlementRole
Indicates that an entity holds a specific role, responsibility, or function within a resettlement process or program.
-
C.
resettlementStart
Indicates the point in time when a process of relocating people or communities to a new place begins.
-
D.
resettledBy
Indicates that an entity has been moved or established anew in a location or context by another agent or authority.
-
E.
resettledAt
Indicates that an entity has moved and established residence or presence at a new location.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.