Triple
T26336348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whittier, Alaska |
E662531
|
entity |
| Predicate | mostResidentsLiveIn |
P128861
|
FINISHED |
| Object | Begich Towers |
—
|
NE NERFINISHED |
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: Begich Towers | Statement: [Whittier, Alaska, mostResidentsLiveIn, Begich Towers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostResidentsLiveIn Context triple: [Whittier, Alaska, mostResidentsLiveIn, Begich Towers]
-
A.
majorPopulationIn
Indicates that a significant portion of a population is located in or primarily associated with a particular place or region.
-
B.
hasResidentPopulation
Indicates that a place or administrative area has a population of people who live there permanently or for an extended period.
-
C.
isMajorResidentialCenterOf
chosen
Indicates that a location serves as a primary hub or main area of residence for the referenced population or region.
-
D.
majorPopulation
Indicates that an entity serves as the primary or most significant population group associated with another entity (such as a place or organization).
-
E.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f6e0dc88190b3eaa4acc7b5bb06 |
completed | May 2, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:36 p.m.