Triple
T9144445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel Gorton |
E219412
|
entity |
| Predicate | secured |
P22516
|
FINISHED |
| Object | Parliamentary charter for Warwick |
—
|
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: Parliamentary charter for Warwick | Statement: [Samuel Gorton, secured, Parliamentary charter for Warwick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secured Context triple: [Samuel Gorton, secured, Parliamentary charter for Warwick]
-
A.
securedVariant
Indicates that one entity is a security-enhanced or more protected version of another entity.
-
B.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
C.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
D.
helpedSecure
chosen
Indicates that one entity contributed to obtaining, protecting, or ensuring the safety or stability of another entity or outcome.
-
E.
safeguard
Indicates taking protective actions to shield someone or something from harm, loss, or danger.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca9166d308190a742ae68371439ee |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:19 p.m.