Triple

T23768350
Position Surface form Disambiguated ID Type / Status
Subject Shishmaref, Alaska E587448 entity
Predicate relocationStatus P146918 FINISHED
Object partially planned but not fully implemented 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: partially planned but not fully implemented | Statement: [Shishmaref, Alaska, relocationStatus, partially planned but not fully implemented]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relocationStatus
Context triple: [Shishmaref, Alaska, relocationStatus, partially planned but not fully implemented]
  • A. preRelocationStatus
    Indicates the condition or state an entity was in prior to being relocated or moved from its original position or context.
  • B. statusAfterRelocation
    Indicates the condition or state an entity has once it has been moved from its original location to a new one.
  • C. resettlementStatus chosen
    Indicates the current stage or condition of an entity’s relocation or re-establishment process in a new place.
  • D. relocatedWithin
    Indicates that an entity has moved from one location to another while remaining within the same broader area or jurisdiction.
  • E. relocated
    Indicates that an entity has moved or been moved from one location or position to another.
  • 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_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.
Created at: April 17, 2026, 7:15 p.m.