Triple
T936219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament of Ireland |
E20199
|
entity |
| Predicate | PoyningsLawEnacted |
P1124
|
FINISHED |
| Object | 1494–1495 |
—
|
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: 1494–1495 | Statement: [Parliament of Ireland, PoyningsLawEnacted, 1494–1495]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PoyningsLawEnacted Context triple: [Parliament of Ireland, PoyningsLawEnacted, 1494–1495]
-
A.
statusOfLondonAct
Indicates the legal or operational status associated with the London Act in relation to a given entity or context.
-
B.
dateOfRoyalAssent
Indicates the specific date on which a proposed law or bill formally receives royal assent and thereby becomes law.
-
C.
dateOfEnactment
chosen
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
D.
legislatedUnder
Indicates that a law, regulation, or policy was created, enacted, or established according to the authority, framework, or provisions of a specific higher-level law or legal regime.
-
E.
enactedAfter
Indicates that one enactment event occurred later in time than another enactment event.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b36558588190a2a9c710073624d1 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29b245c8190b143f28b77fede3c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.