Triple
T26591075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Hardenberg |
E667355
|
entity |
| Predicate | traditionalEstateType |
P114979
|
FINISHED |
| Object | manorial estates |
—
|
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: manorial estates | Statement: [von Hardenberg, traditionalEstateType, manorial estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalEstateType Context triple: [von Hardenberg, traditionalEstateType, manorial estates]
-
A.
estateTypeHistorically
chosen
Indicates that one entity historically had a particular type or classification of estate, even if that estate type may have changed or no longer exists in the present.
-
B.
traditionalHousingRegion
Indicates the region where a group’s customary or historically established housing patterns are typically found.
-
C.
countryEstateType
Indicates the classification or category of an estate based on the country in which it is located or to which it belongs.
-
D.
countryEstate
Indicates that a particular estate or property is located within or belongs to a specified country.
-
E.
nobleEstate
Indicates that an entity is a noble’s estate or property associated with nobility.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 27, 2026, 2:08 a.m.