Triple
T5856180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip, son of Frederick II and Isabella of England |
E130158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 13th-century German nobility |
C2995
|
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 German nobility Context triple: [Philip, son of Frederick II and Isabella of England, instanceOf, 13th-century German nobility]
-
A.
member of German nobility
A member of German nobility is an individual belonging to a historically privileged social class in German-speaking regions, typically holding hereditary titles, land, and social status recognized under traditional aristocratic systems.
-
B.
Austrian noble
An Austrian noble is a member of the historical aristocracy of Austria, typically holding hereditary titles, land, and social privileges within the Habsburg and later Austrian realms.
-
C.
German noble
chosen
A German noble is a member of the historical aristocratic class in German-speaking regions, traditionally holding hereditary titles, land, and social privileges within the feudal and later monarchical systems.
-
D.
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.
-
E.
medieval English noble dynasty
A medieval English noble dynasty is a powerful hereditary family line that held titles, lands, and political influence across generations in England during the Middle Ages.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:55 p.m.