Triple
T26741022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Bismarck |
E674254
|
entity |
| Predicate | hasFamilyHeadResidence |
P55861
|
FINISHED |
| Object | Friedrichsruh estate |
—
|
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: Friedrichsruh estate | Statement: [von Bismarck, hasFamilyHeadResidence, Friedrichsruh estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyHeadResidence Context triple: [von Bismarck, hasFamilyHeadResidence, Friedrichsruh estate]
-
A.
hasFamilyHead
Indicates that one entity serves as the primary head or leader of another entity’s family unit.
-
B.
hasFamilyHomeAt
chosen
Indicates that an entity has its family residence or primary household located at a specified place.
-
C.
hasRulingFamilyResidence
Indicates that a location serves as the primary home or official residence of a ruling family.
-
D.
residenceAcquiredByHead
Indicates that a residence was obtained or established through the actions or status of the household head.
-
E.
hasParentHouse
Indicates that an entity is associated with or belongs to a specific parent house within a hierarchical or familial structure.
- 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_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 3:49 a.m.