Triple
T14915452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephraim, Wisconsin |
E371369
|
entity |
| Predicate | hasBuildingColorTradition |
P31081
|
FINISHED |
| Object | white exteriors |
—
|
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: white exteriors | Statement: [Ephraim, Wisconsin, hasBuildingColorTradition, white exteriors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingColorTradition Context triple: [Ephraim, Wisconsin, hasBuildingColorTradition, white exteriors]
-
A.
hasTraditionalColors
Indicates that an entity is associated with colors that are traditionally or customarily linked to it.
-
B.
traditionalHomeColor
chosen
Indicates the customary or historically typical color associated with a home in a given cultural or regional tradition.
-
C.
buildingColor
Indicates the color or predominant exterior hue associated with a building.
-
D.
hasSuperstructureColor
Indicates that one entity has a superstructure whose color is the value specified by the other entity.
-
E.
hasTraditionalHouseStyle
Indicates that an entity possesses or is characterized by a traditional style of house or residential architecture.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded61f1d488190995f847f84d72cdc |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:28 a.m.