Triple
T32885026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragsholm Castle |
E841172
|
entity |
| Predicate | postReformationOwner |
P162170
|
FINISHED |
| Object | Danish Crown |
—
|
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: Danish Crown | Statement: [Dragsholm Castle, postReformationOwner, Danish Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postReformationOwner Context triple: [Dragsholm Castle, postReformationOwner, Danish Crown]
-
A.
ownedByAfterReformation
chosen
Indicates that one entity became the owner of another entity after the historical period of the Reformation.
-
B.
postReformationDenomination
Indicates that one religious group or entity belongs to, or is associated with, a Christian denomination that emerged after the Protestant Reformation.
-
C.
underwentReformation
Indicates that an entity experienced a significant process of change, restructuring, or reform that altered its previous state or practices.
-
D.
laterReformedAs
Indicates that an entity was subsequently reorganized, renamed, or transformed into another entity at a later time.
-
E.
reformedOn
Indicates that an entity underwent a reform, change, or restructuring at a specific point in time or on a particular date.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:18 a.m.