Triple
T31980057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teutberga of Arles |
E816551
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 9th-century noblewoman |
C57620
|
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: 9th-century noblewoman Context triple: [Teutberga of Arles, instanceOf, 9th-century noblewoman]
-
A.
19th-century noblewoman
A 19th-century noblewoman is an upper-class woman of aristocratic birth or marriage whose life is shaped by strict social hierarchies, elaborate etiquette, and limited but influential roles in family, politics, and culture.
-
B.
Georgian noblewoman
A Georgian noblewoman is an aristocratic woman from the historical region of Georgia, typically characterized by high social status, landownership, and influence within the political and cultural life of Georgian society.
-
C.
13th-century noblewoman
A 13th-century noblewoman is an aristocratic woman of medieval Europe who holds social status and influence through lineage, marriage, and land-based power within a feudal hierarchy.
-
D.
11th-century noblewoman
An 11th-century noblewoman is a high-born female member of medieval European aristocracy whose life centers on managing estates, forging political alliances through marriage, and upholding social and religious obligations within a feudal hierarchy.
-
E.
12th-century noblewoman
A 12th-century noblewoman is an aristocratic woman of medieval Europe who wields social, economic, and sometimes political influence through landholding, marriage alliances, and the management of her household and estates within a feudal hierarchy.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:11 a.m.