Triple
T3559726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Brunswick-Bevern |
E75305
|
entity |
| Predicate | hasNobleStyle |
P44258
|
FINISHED |
| Object | Serene Highness |
—
|
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: Serene Highness | Statement: [House of Brunswick-Bevern, hasNobleStyle, Serene Highness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobleStyle Context triple: [House of Brunswick-Bevern, hasNobleStyle, Serene Highness]
-
A.
hasRoyalStatus
chosen
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
B.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
C.
hasHeraldicAttitude
Indicates that an entity (typically an animal or figure in heraldry) is depicted with a specific standardized posture or stance in a coat of arms.
-
D.
honourStyle
Indicates a relationship where one entity follows, respects, or upholds the manner, customs, or stylistic approach associated with another.
-
E.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc089270c81908bc200c84fe1592e |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.