Triple
T21205281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Iburg |
E522559
|
entity |
| Predicate | historicUseOfIburgCastle |
P143536
|
FINISHED |
| Object | residence of the Prince-Bishops of Osnabrück |
—
|
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: residence of the Prince-Bishops of Osnabrück | Statement: [Bad Iburg, historicUseOfIburgCastle, residence of the Prince-Bishops of Osnabrück]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicUseOfIburgCastle Context triple: [Bad Iburg, historicUseOfIburgCastle, residence of the Prince-Bishops of Osnabrück]
-
A.
castleCurrentUse
Indicates the present-day function or role that the castle serves.
-
B.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
-
C.
eraOfMainCastle
Indicates the historical period or era during which the main castle associated with an entity was built, used, or most prominent.
-
D.
fortressUsedAs
Indicates that one entity functions or is employed in the role of a fortress for another entity or purpose.
-
E.
largestInhabitedCastleIn
Indicates that a castle is the largest inhabited castle located within a given geographic area or region.
- F. None of above. chosen
Provenance (4 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734342e9081909e241bed54dbc0b4 |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5fa92a2448190896c022dd27511ad |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 16, 2026, 3:20 p.m.