Triple
T20725896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Abbey of Herford |
E509433
|
entity |
| Predicate | gainedImperialStatus |
P110758
|
FINISHED |
| Object | circa 1147 |
—
|
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: circa 1147 | Statement: [Imperial Abbey of Herford, gainedImperialStatus, circa 1147]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedImperialStatus Context triple: [Imperial Abbey of Herford, gainedImperialStatus, circa 1147]
-
A.
wasMadeCoEmperorBy
Indicates that one entity was elevated to the rank of co-emperor through the action or decision of another entity.
-
B.
establishedAsSignoria
Indicates that an entity was instituted or set up as a signoria, i.e., a governing lordship or ruling authority over a city or territory.
-
C.
ascendedToThroneAs
Indicates that an individual assumed royal power and officially became the reigning monarch under a specific title or role.
-
D.
wasElevatedTo
chosen
Indicates that an entity was promoted or raised to a higher rank, status, or position.
-
E.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e7aabc819084f9e9fd45e877fd |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:29 p.m.