Triple
T6425815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohemond VI of Antioch |
E128055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 13th-century noble |
C13886
|
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: 13th-century noble Context triple: [Bohemond VI of Antioch, instanceOf, 13th-century noble]
-
A.
14th-century English noble
A 14th-century English noble is a high-ranking member of the medieval English aristocracy who holds land from the king, exercises local political and military authority, and participates in courtly and feudal obligations within a rigidly hierarchical society.
-
B.
13th-century monarch
A 13th-century monarch is a sovereign ruler who governed a kingdom or empire during the 1200s, navigating feudal power structures, dynastic politics, and often religious conflicts to maintain authority and territorial control.
-
C.
13th-century person
chosen
A 13th-century person is an individual who lived during the 1200s, shaped by the social, political, religious, and technological contexts of the High Middle Ages.
-
D.
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.
-
E.
12th-century monarch
A 12th-century monarch is a sovereign ruler who governed a kingdom or empire during the 1100s, wielding political, military, and often religious authority within a feudal and dynastic framework.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:43 p.m.