Triple
T31251394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Speyer |
E796827
|
entity |
| Predicate | heldOfficeUntilCentury |
P31300
|
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: [Prince-Bishop of Speyer, heldOfficeUntilCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldOfficeUntilCentury Context triple: [Prince-Bishop of Speyer, heldOfficeUntilCentury, 19th century]
-
A.
ruledUntilCentury
chosen
Indicates that a ruling relationship held by an entity continued in effect up to (but not necessarily including) a specified century.
-
B.
flourishedUntilCentury
Indicates the last century during which an entity (such as a person, culture, or institution) was active, prominent, or at its peak before declining or ceasing to flourish.
-
C.
cameToPowerInCentury
Indicates that an entity assumed ruling authority or control during a specified century.
-
D.
servedInCentury
Indicates that an entity’s period of service or activity took place during a specified century.
-
E.
activeUntilCentury
Indicates that an entity remains active or in effect up to and including 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:11 p.m.