Triple
T4730193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Roermond |
E104985
|
entity |
| Predicate | suppressedInCentury |
P10731
|
FINISHED |
| Object | 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: 19th century | Statement: [Bishopric of Roermond, suppressedInCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppressedInCentury Context triple: [Bishopric of Roermond, suppressedInCentury, 19th century]
-
A.
supersededInCentury
Indicates that one entity has been replaced or rendered obsolete by another during a specified century.
-
B.
declinedAfterCentury
Indicates that something experienced a reduction, deterioration, or loss of prominence after the end of a specified century.
-
C.
suppressionYear
Indicates the year in which the referenced activity, expression, or entity was formally suppressed, halted, or forcibly discontinued.
-
D.
suppressedDuring
chosen
Indicates that one event, action, or state is actively prevented, inhibited, or held back while another specified event, condition, or time period is occurring.
-
E.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6220071881909670c89d072ffb6d |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.