Triple
T15159842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis V, Landgrave of Hesse-Darmstadt |
E362178
|
entity |
| Predicate | noble style |
P76052
|
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: [Louis V, Landgrave of Hesse-Darmstadt, noble style, Serene Highness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noble style Context triple: [Louis V, Landgrave of Hesse-Darmstadt, noble style, Serene Highness]
-
A.
aristocraticStyle
Indicates a relationship where something exhibits or embodies the manner, tastes, or aesthetic typically associated with aristocracy or the aristocratic class.
-
B.
honourStyle
Indicates a relationship where one entity follows, respects, or upholds the manner, customs, or stylistic approach associated with another.
-
C.
nobleTitleStyle
chosen
Indicates the specific form or style in which a person's noble title is expressed or formally rendered.
-
D.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
E.
honorStyle
Indicates the manner or level of respect, formality, or honor expressed toward or between entities.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060dd71881908ecc4a4f52d438a5 |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.