Triple
T18639602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Village of Caledonia, Wisconsin |
E455646
|
entity |
| Predicate | isNamedCaledonia |
P72125
|
FINISHED |
| Object | after historical name for Scotland |
—
|
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: after historical name for Scotland | Statement: [Village of Caledonia, Wisconsin, isNamedCaledonia, after historical name for Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedCaledonia Context triple: [Village of Caledonia, Wisconsin, isNamedCaledonia, after historical name for Scotland]
-
A.
hasNameInScots
Indicates that an entity has a specific name or designation expressed in the Scots language.
-
B.
hasCelticName
chosen
Indicates that an entity possesses a name that is of Celtic origin or in a Celtic language.
-
C.
GaelicName
Indicates that an entity has a name expressed in the Gaelic language.
-
D.
hasCelticNameType
Indicates that an entity is associated with a specific type or category of Celtic name.
-
E.
hasColonialName
Indicates that an entity is known by, or has been assigned, a name originating from a colonial power or colonial period.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fcbe3088190849f60b09d1e7e4b |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.