Triple
T19709612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Cromwell |
E473305
|
entity |
| Predicate | heldPowerFrom |
P29191
|
FINISHED |
| Object | 1653 |
—
|
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: 1653 | Statement: [House of Cromwell, heldPowerFrom, 1653]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldPowerFrom Context triple: [House of Cromwell, heldPowerFrom, 1653]
-
A.
heldTemporalPower
chosen
Indicates that an entity exercised governing or authoritative control over another entity or domain during a specific period of time.
-
B.
seizedPowerBy
Indicates that one entity took control or authority from another, typically through force, coercion, or other non-consensual means.
-
C.
heldPowerAlongside
Indicates that two or more entities simultaneously shared and exercised governing or influential authority during the same period.
-
D.
heldExecutivePowerUntil
Indicates that an entity exercised executive authority or leadership in a role or office up to a specified end date or point in time.
-
E.
seizedPowerAfter
Indicates that one entity took control or authority from another entity following a specified event or point in time.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64406f9808190acd74aa03c392eb0 |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.