Triple
T38285618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Town of Gammelstad, Luleå |
E1022197
|
entity |
| Predicate | paintColorOfCottages |
P46808
|
FINISHED |
| Object | Falu red |
—
|
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: Falu red | Statement: [Church Town of Gammelstad, Luleå, paintColorOfCottages, Falu red]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paintColorOfCottages Context triple: [Church Town of Gammelstad, Luleå, paintColorOfCottages, Falu red]
-
A.
traditionalHomeColor
Indicates the customary or historically typical color associated with a home in a given cultural or regional tradition.
-
B.
buildingColor
chosen
Indicates the color or predominant exterior hue associated with a building.
-
C.
hasHouseColor
Indicates that an entity possesses a house whose exterior is characterized by a specific color.
-
D.
traditionalHomeShortsColor
Indicates the typical or customary color of the home team’s shorts in a traditional or standard uniform set.
-
E.
homeColorsDominant
Indicates that the primary or most prominent colors associated with a subject’s home (such as a team’s home uniform or a building’s main color scheme) are specified or emphasized.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.