Triple
T33072315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Hohenlohe |
E846264
|
entity |
| Predicate | typeOfImperialEstate |
P33508
|
FINISHED |
| Object | Reichsstand |
—
|
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: Reichsstand | Statement: [Principality of Hohenlohe, typeOfImperialEstate, Reichsstand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfImperialEstate Context triple: [Principality of Hohenlohe, typeOfImperialEstate, Reichsstand]
-
A.
establishedAsImperialEstate
Indicates that something has been formally designated or set up as an imperial estate under the authority of an empire.
-
B.
heldImperialEstate
Indicates that an entity possessed or controlled land or property classified as an imperial estate under a particular imperial authority.
-
C.
hasEstateType
chosen
Indicates that an entity possesses or is associated with a particular category or type of estate.
-
D.
typeOfEmpire
Indicates the specific kind or classification of empire that an entity belongs to or represents.
-
E.
daimyoResidence
Indicates that a location serves or served as the official residence of a daimyo (feudal lord).
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a009a0e1fa481909ed881012009b268 |
completed | May 10, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_6a0092e9fcb08190a966d720684f25ec |
completed | May 10, 2026, 2:15 p.m. |
Created at: May 1, 2026, 1:25 a.m.