Triple
T23768349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shishmaref, Alaska |
E587448
|
entity |
| Predicate | hasRelocationPlan |
P153881
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shishmaref, Alaska, hasRelocationPlan, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelocationPlan Context triple: [Shishmaref, Alaska, hasRelocationPlan, yes]
-
A.
hasReconstructionPlan
Indicates that there exists a defined plan or strategy for rebuilding, restoring, or reconstructing a given entity or system.
-
B.
hasRelocation
Indicates that one entity is moved, transferred, or reassigned from one location or context to another.
-
C.
proposesRelocationTo
Indicates that one entity suggests or recommends that another entity move or be moved to a different location.
-
D.
relocationAnnounced
Indicates that an official communication has been made stating that an entity will move from one location to another.
-
E.
requiredRelocationFrom
Indicates that one entity mandates or necessitates the relocation of another entity away from a specified source location or context.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c4638b248190b512841493778483 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:15 p.m.