Triple
T26336347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whittier, Alaska |
E662531
|
entity |
| Predicate | primaryResidentialBuilding |
P135916
|
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, primaryResidentialBuilding, Begich Towers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryResidentialBuilding Context triple: [Whittier, Alaska, primaryResidentialBuilding, Begich Towers]
-
A.
ownedResidence
Indicates that one entity has ownership of a dwelling or place of residence associated with another entity.
-
B.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
C.
hasResidentialBuilding
Indicates that an entity possesses, contains, or is associated with a residential building as part of its properties or components.
-
D.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
E.
isResidentialBuildingIn
chosen
Indicates that a residential building is located within or belongs to a specified geographic area or administrative region.
- 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_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: April 26, 2026, 10:36 p.m.