Triple

T34775597
Position Surface form Disambiguated ID Type / Status
Subject Old Harbor Airport E1002495 entity
Predicate locatedIn P40 FINISHED
Object Old Harbor, Alaska
Old Harbor, Alaska is a small Alutiiq village on Kodiak Island known for its subsistence lifestyle, fishing-based economy, and scenic coastal setting.
E2159307 NE 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: Old Harbor, Alaska | Statement: [Old Harbor Airport, locatedIn, Old Harbor, Alaska]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Old Harbor, Alaska
Triple: [Old Harbor Airport, locatedIn, Old Harbor, Alaska]
Generated description
Old Harbor, Alaska is a small Alutiiq village on Kodiak Island known for its subsistence lifestyle, fishing-based economy, and scenic coastal setting.

Provenance (5 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_69f76db30a108190bb57ca95b873e5bb completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77a3dc54c81908584f71243fd1673 completed May 3, 2026, 4:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38a4c9809c819096c68b3836322170 completed June 22, 2026, 2:58 a.m.
NEDg Description generation batch_6a38a57d5e2c81908a749015ac6fcd7f completed June 22, 2026, 3:01 a.m.
NED2 Entity disambiguation (via description) batch_6a38a5fa291c81909955855947ef19d5 completed June 22, 2026, 3:03 a.m.
Created at: May 3, 2026, 3:59 p.m.