Triple
T1528049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New World |
E32380
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical geographic term |
C263
|
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 geographic term Context triple: [New World, instanceOf, historical geographic term]
-
A.
historical place name
A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
-
B.
geographical concept
A geographical concept is an abstract idea or principle used to understand, describe, and analyze the spatial characteristics, relationships, and processes of the Earth's physical and human environments.
-
C.
historic region
chosen
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.
-
D.
geographical region
A geographical region is a defined area of the Earth's surface characterized by shared physical, cultural, political, or environmental features that distinguish it from surrounding areas.
-
E.
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.
- F. None of above.
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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:26 p.m.