Triple
T28039266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hooper Bay Yup'ik community |
E708492
|
entity |
| Predicate | contemporaryHousing |
P172128
|
FINISHED |
| Object | wood-frame houses |
—
|
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: wood-frame houses | Statement: [Hooper Bay Yup'ik community, contemporaryHousing, wood-frame houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryHousing Context triple: [Hooper Bay Yup'ik community, contemporaryHousing, wood-frame houses]
-
A.
designedBuildingNowHousing
Indicates that an entity designed a building which is currently being used as a housing facility.
-
B.
contemporary
Indicates that two entities exist, occur, or are active during the same time period or historical era.
-
C.
contemporaryTendency
Indicates that one entity reflects, aligns with, or exemplifies a prevailing trend, style, or tendency of the same time period as another entity.
-
D.
homeCountryModern
Indicates that one entity is the modern-day country that serves as the home or origin country of the other entity.
-
E.
postwarResidence
Indicates the place where an entity lived or was based during the period following a specified war.
- F. None of above. chosen
Provenance (4 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 27, 2026, 8:23 p.m.