Triple
T8054371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Marriages Act 1772 |
E187757
|
entity |
| Predicate | inForceInYear |
P6526
|
FINISHED |
| Object | 1800 |
—
|
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: 1800 | Statement: [Royal Marriages Act 1772, inForceInYear, 1800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inForceInYear Context triple: [Royal Marriages Act 1772, inForceInYear, 1800]
-
A.
inForceInPeriod
Indicates that something (such as a rule, contract, or condition) is valid, applicable, or legally effective during a specified time period.
-
B.
inForceIn
chosen
Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
-
C.
cameIntoForceInYear
Indicates that a law, agreement, or formal measure became legally effective or operational in a specified calendar year.
-
D.
inForce
Indicates that a rule, law, agreement, or condition is currently valid, active, and being applied or enforced.
-
E.
hasNumberInYear
Indicates that a specific number is associated with or occurs within a given year.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f9fb8dc8190bacc1f66ddfd1cbf |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.