Triple
T3185523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Laws of 1542 |
E66688
|
entity |
| Predicate | partiallyRevokedIn |
P13261
|
FINISHED |
| Object | 1545 |
—
|
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: 1545 | Statement: [New Laws of 1542, partiallyRevokedIn, 1545]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyRevokedIn Context triple: [New Laws of 1542, partiallyRevokedIn, 1545]
-
A.
partiallyRevokedBy
chosen
Indicates that an existing grant, permission, or authorization has been revoked in part (but not entirely) by another action or decision.
-
B.
partiallyReauthorizedBy
Indicates that an existing authorization or approval has been renewed or extended only in part by another entity or action, rather than fully reauthorized.
-
C.
partiallyInvalidatedBy
Indicates that the validity or effect of something is reduced or weakened, but not completely nullified, by another action or entity.
-
D.
canBeRevoked
Indicates that a previously granted status, permission, or agreement is subject to being withdrawn or canceled.
-
E.
reopenedPartially
Indicates that an entity that was previously closed or inactive has been opened again, but only to a limited or incomplete extent.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6c1341081909793f8d05fddfd5e |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.