Triple
T36797500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longueville |
E909223
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical territorial domain |
C12509
|
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 territorial domain Context triple: [Longueville, instanceOf, historical territorial domain]
-
A.
ancient territory
An ancient territory is a historically defined geographic region that was controlled, inhabited, or claimed by past civilizations or cultures, often with distinct political, cultural, or religious significance.
-
B.
historical geographic entity
chosen
A historical geographic entity is a spatially bounded area whose location, extent, or political status has changed or ceased to exist over time, but which is recognized for its past geographic or administrative significance.
-
C.
ethnic territory
An ethnic territory is a geographically defined area predominantly inhabited by a particular ethnic group, where shared cultural, linguistic, or historical traits form the basis of collective identity and claims to space.
-
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.
history of a region
A history of a region is a structured account of the social, political, economic, and cultural developments that have shaped a specific geographic area over time.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.