Triple
T25711683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green County, Wisconsin |
E644748
|
entity |
| Predicate | hasVillageNickname |
P58505
|
FINISHED |
| Object | New Glarus, Wisconsin as "America’s Little Switzerland" |
—
|
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: New Glarus, Wisconsin as "America’s Little Switzerland" | Statement: [Green County, Wisconsin, hasVillageNickname, New Glarus, Wisconsin as "America’s Little Switzerland"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVillageNickname Context triple: [Green County, Wisconsin, hasVillageNickname, New Glarus, Wisconsin as "America’s Little Switzerland"]
-
A.
isVillageNameOf
Indicates that a given name is the official or recognized name of a particular village.
-
B.
nicknameOfTown
chosen
Indicates that one entity is a nickname or informal name used to refer to a particular town.
-
C.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
D.
isVillage
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
-
E.
canAppearWithVillageNameOnLabel
Indicates that an entity is permitted to be displayed together with a village name on a product label.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 9:16 p.m.