Triple
T23386651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limburg-Styrum-Bronckhorst branch |
E593900
|
entity |
| Predicate | hasNobleHouseType |
P67660
|
FINISHED |
| Object | German-Dutch nobility |
—
|
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-Dutch nobility | Statement: [Limburg-Styrum-Bronckhorst branch, hasNobleHouseType, German-Dutch nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobleHouseType Context triple: [Limburg-Styrum-Bronckhorst branch, hasNobleHouseType, German-Dutch nobility]
-
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.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
C.
hasNobleHouseOrigin
Indicates that an entity originates from, or is ancestrally associated with, a particular noble house.
-
D.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
E.
evaluatesAsNoble
Indicates that an entity is judged or classified as having noble status or qualities.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a498286c8190abfa381649812cf0 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.