Triple
T31551912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amana, Iowa |
E805025
|
entity |
| Predicate | communalHistory |
P173774
|
FINISHED |
| Object | former religious communal society |
—
|
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: former religious communal society | Statement: [Amana, Iowa, communalHistory, former religious communal society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communalHistory Context triple: [Amana, Iowa, communalHistory, former religious communal society]
-
A.
historicalSociety
Indicates that an entity is a society or organization dedicated to preserving, studying, or promoting history.
-
B.
sharesHistoricalLegacyOf
Indicates that one entity is connected to, or participates in, the same historical legacy, tradition, or heritage as another entity.
-
C.
urbanHistoryFeature
Indicates a feature that plays a significant role in the historical development, events, or evolution of an urban area.
-
D.
regionHistory
Indicates that there exists a historical or past association between a subject and a specific geographic or administrative region.
-
E.
includesTownHistory
Indicates that something contains or covers information about the history of a town.
- F. None of above. chosen
Provenance (4 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: April 30, 2026, 10:11 p.m.