Triple
T27291151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Switzerland County, Indiana |
E688629
|
entity |
| Predicate | hasHistoricRiverTowns |
P25415
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Switzerland County, Indiana, hasHistoricRiverTowns, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricRiverTowns Context triple: [Switzerland County, Indiana, hasHistoricRiverTowns, true]
-
A.
hasRiverPortHistory
chosen
Indicates that an entity has a historical association with functioning as a river port or hosting river port activities.
-
B.
hasTownOnRiver
Indicates that a town is situated on or directly adjacent to a particular river.
-
C.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular river.
-
D.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
E.
hasHistoricVillagesAlong
Indicates that a route, path, or geographic feature has historic villages located along its course or in close proximity to it.
- 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_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 27, 2026, 11:15 a.m.