Triple
T26741014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Bismarck |
E674254
|
entity |
| Predicate | hereditaryTitleLinked |
P914
|
FINISHED |
| Object | Fürst von Bismarck |
—
|
NE NERFINISHED |
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: Fürst von Bismarck | Statement: [von Bismarck, hereditaryTitleLinked, Fürst von Bismarck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryTitleLinked Context triple: [von Bismarck, hereditaryTitleLinked, Fürst von Bismarck]
-
A.
hereditaryTitleFor
Indicates that one entity is a hereditary title that is held by, or associated with, another entity, typically passed down through a family line.
-
B.
associatedNobleTitle
chosen
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
C.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
D.
nobleTitleHeirTo
Indicates that one entity is the designated heir to the noble title held by another entity.
-
E.
recognizedHeirTitle
Indicates that an individual is formally acknowledged as the legitimate holder or successor of a specific hereditary title.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6187e939c81908e5da8b43227a444 |
completed | May 2, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:49 a.m.