Triple
T291951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act of Settlement 1701 |
E6012
|
entity |
| Predicate | royalAssent |
P8385
|
FINISHED |
| Object | 1701 |
—
|
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: 1701 | Statement: [Act of Settlement 1701, royalAssent, 1701]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalAssent Context triple: [Act of Settlement 1701, royalAssent, 1701]
-
A.
royalAssentGivenBy
Indicates that a formal approval or authorization, typically of legislation or an official act, is granted by a monarch or sovereign authority.
-
B.
requiresRoyalAssent
Indicates that an action, decision, or legislative measure must receive formal approval from a monarch or royal representative before it becomes valid or effective.
-
C.
dateOfRoyalAssent
chosen
Indicates the specific date on which a proposed law or bill formally receives royal assent and thereby becomes law.
-
D.
signedUnderMonarch
Indicates that a document or agreement was formally signed during the reign or authority of a specific monarch.
-
E.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e934b4408190b53a17f57a02df65 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.