Triple
T792797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marthasville |
E16951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical place name |
C4613
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical place name Context triple: [Marthasville, instanceOf, historical place name]
-
A.
historical ethnonym
A historical ethnonym is a name or label historically used to designate a particular ethnic group, people, or population, often reflecting past cultural, political, or linguistic contexts that may differ from present-day usage.
-
B.
geographical names authority
A geographical names authority is an entity or system responsible for standardizing, maintaining, and providing authoritative information on the official names and spellings of geographic places.
-
C.
historic designation
A historic designation is an official recognition granted to a place, structure, or object for its significant historical, architectural, cultural, or archaeological value, often providing it with legal protections and conservation guidelines.
-
D.
historic region
A historic region is a geographically defined area recognized for its significant past events, cultural heritage, or historical identity that has shaped its development over time.
-
E.
historic monument
A historic monument is a significant structure, site, or object preserved for its cultural, architectural, or historical importance, symbolizing and commemorating events, people, or eras of the past.
- F. None of above. chosen
Provenance (1 batch)
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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:38 p.m.