Triple
T26160375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karpniki Castle |
E660091
|
entity |
| Predicate | hasOwnerInPeriod |
P128181
|
FINISHED |
| Object | Prussian royalty in the 19th century |
—
|
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: Prussian royalty in the 19th century | Statement: [Karpniki Castle, hasOwnerInPeriod, Prussian royalty in the 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnerInPeriod Context triple: [Karpniki Castle, hasOwnerInPeriod, Prussian royalty in the 19th century]
-
A.
hasOwnerInThePast
chosen
Indicates that an entity was owned by another entity at some time in the past, but not necessarily in the present.
-
B.
hasOwnerWhoLaterOwned
Indicates that an entity is owned by someone who, at a later time, also became the owner of another specified entity.
-
C.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
D.
promotionOwnerAtTime
Indicates that a specified entity is the owner or controller of a particular promotion during a given time period.
-
E.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c15e9848190ad5dcdb8879aadf7 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:29 p.m.