Triple

T7706805
Position Surface form Disambiguated ID Type / Status
Subject Galena, Alaska E174638 entity
Predicate hasRebuildingEffort P28319 FINISHED
Object post-2013 flood reconstruction 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: post-2013 flood reconstruction | Statement: [Galena, Alaska, hasRebuildingEffort, post-2013 flood reconstruction]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRebuildingEffort
Context triple: [Galena, Alaska, hasRebuildingEffort, post-2013 flood reconstruction]
  • A. hasReconstructionWork chosen
    Indicates that an entity is undergoing, has undergone, or is associated with reconstruction or restoration work.
  • B. haveReconstructionWork
    Indicates that an entity is undergoing or is associated with reconstruction or restoration work.
  • C. hasRebuilt
    Indicates that an entity has restored, reconstructed, or built again something that previously existed or was damaged or destroyed.
  • D. rebuiltFor
    Indicates that one entity has been reconstructed, renovated, or modified specifically to serve the needs, purposes, or use of another entity.
  • E. rebuiltUnder
    Indicates that an entity was reconstructed or restored while being subject to the authority, control, or governance of another entity.
  • 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_69c6995b3e8c8190833108f883d5f53c completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c702ebb7448190ae8d47fe0cbb0907 completed March 27, 2026, 10:21 p.m.
PD Predicate disambiguation batch_69c701683dec8190be9861e592aa8ce0 completed March 27, 2026, 10:15 p.m.
Created at: March 27, 2026, 4:04 p.m.