Triple
T35550894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Schweidnitz |
E1027357
|
entity |
| Predicate | nobilityTradition |
P174116
|
FINISHED |
| Object | German 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 nobility | Statement: [von Schweidnitz, nobilityTradition, German nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobilityTradition Context triple: [von Schweidnitz, nobilityTradition, German nobility]
-
A.
nobilityCulture
Indicates a relationship where a group’s customs, values, or practices are specifically associated with or characteristic of the nobility.
-
B.
nobilitySystem
Indicates a social or political structure in which individuals are ranked by hereditary titles or noble status.
-
C.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
D.
nobleTradition
chosen
Indicates a relationship where an entity upholds, follows, or is associated with a long-established and esteemed custom or practice.
-
E.
aristocraticLegacy
Indicates that an entity inherits or is influenced by the traditions, status, or privileges associated with aristocratic lineage.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.