Triple
T13406538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lippe-Biesterfeld |
E319973
|
entity |
| Predicate | nobleHouseCategory |
P67660
|
FINISHED |
| Object | German noble family |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: German noble family | Statement: [Lippe-Biesterfeld, nobleHouseCategory, German noble family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleHouseCategory Context triple: [Lippe-Biesterfeld, nobleHouseCategory, German noble family]
-
A.
nobleHouseType
chosen
Indicates the specific category or classification of a noble house (e.g., royal, ducal, baronial) within a hierarchy or system of nobility.
-
B.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
-
C.
nobleHouseInfluence
Indicates the degree to which a noble house exerts power, control, or sway over people, events, or territories.
-
D.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
E.
notableNobleFaction
Indicates that a noble is significantly associated with or belongs to a particularly prominent or influential noble faction.
- F. None of above.
Provenance (3 batches)
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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae4be498819094798473a1bfd853 |
completed | April 12, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:35 p.m.