Triple
T30283483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Schlebrügge |
E770166
|
entity |
| Predicate | hasAristocraticOrigin |
P166694
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [von Schlebrügge, hasAristocraticOrigin, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAristocraticOrigin Context triple: [von Schlebrügge, hasAristocraticOrigin, true]
-
A.
aristocraticOrigin
chosen
Indicates that an entity originates from, or is derived from, an aristocratic or noble background.
-
B.
hasRelativeInAristocracy
Indicates that an entity has at least one relative who belongs to the aristocracy or noble class.
-
C.
hasNobleHouseOrigin
Indicates that an entity originates from, or is ancestrally associated with, a particular noble house.
-
D.
aristocraticLegacy
Indicates that an entity inherits or is influenced by the traditions, status, or privileges associated with aristocratic lineage.
-
E.
aristocraticFamilyRise
Indicates the process or circumstance in which an aristocratic family gains power, status, or prominence within a social or political hierarchy.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 29, 2026, 7:45 p.m.