Triple
T27291171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Switzerland County, Indiana |
E688629
|
entity |
| Predicate | hasNamedForEthnicGroup |
P147326
|
FINISHED |
| Object | Swiss immigrants |
—
|
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: Swiss immigrants | Statement: [Switzerland County, Indiana, hasNamedForEthnicGroup, Swiss immigrants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamedForEthnicGroup Context triple: [Switzerland County, Indiana, hasNamedForEthnicGroup, Swiss immigrants]
-
A.
ethnicGroupNamed
Indicates that an ethnic group bears or is identified by a particular name.
-
B.
hasEthnicNameType
Indicates that an entity’s name is classified according to a specific ethnic or cultural naming type.
-
C.
hasRecognizedEthnicGroup
Indicates that an entity includes or is associated with an ethnic group that is officially or socially recognized as distinct.
-
D.
hasEthnicGroupDocumented
chosen
Indicates that an entity has a specific ethnic group recorded or documented as being associated with it.
-
E.
isEthnonymFor
Indicates that one term is the ethnonym (name of a people or ethnic group) used to refer to another entity.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 11:15 a.m.