Triple
T358746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Parliament |
E7801
|
entity |
| Predicate | reasonForSummons |
P6484
|
FINISHED |
| Object | need to raise funds for the Bishops’ Wars |
—
|
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: need to raise funds for the Bishops’ Wars | Statement: [Long Parliament, reasonForSummons, need to raise funds for the Bishops’ Wars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForSummons Context triple: [Long Parliament, reasonForSummons, need to raise funds for the Bishops’ Wars]
-
A.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
-
B.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
-
C.
reasonForCreation
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
D.
originalReason
chosen
Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
-
E.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebb248608190b060553219616043 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e95aeed48190b5e48865cc964938 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.