Triple
T20891567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Abbey of Burtscheid |
E514419
|
entity |
| Predicate | imperialImmediateStatus |
P40055
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Imperial Abbey of Burtscheid, imperialImmediateStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imperialImmediateStatus Context triple: [Imperial Abbey of Burtscheid, imperialImmediateStatus, yes]
-
A.
actualStatus
Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
-
B.
reignStatus
Indicates the status or condition of an entity’s period of rule or governance, such as whether it is ongoing, completed, or otherwise characterized.
-
C.
legalStatusInEmpire
chosen
Indicates the formal legal standing or classification an entity holds within a particular empire’s legal and administrative system.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
strategicStatus
Indicates the strategic condition or importance of an entity within a broader plan, context, or objective.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05e307081908f1d044e877017ec |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.