Triple
T6906726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor of Vermont |
E159830
|
entity |
| Predicate | mayGrant |
P74042
|
FINISHED |
| Object | reprieves and pardons under Vermont law |
—
|
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: reprieves and pardons under Vermont law | Statement: [Governor of Vermont, mayGrant, reprieves and pardons under Vermont law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayGrant Context triple: [Governor of Vermont, mayGrant, reprieves and pardons under Vermont law]
-
A.
mustGrant
Indicates that one party is obligated to give or allow something (such as a right, permission, or resource) to another party.
-
B.
mayRuleOver
Indicates that one entity has the potential or permission to exercise authority or governance over another entity.
-
C.
maySign
Indicates that an entity has the permission or authority to sign a document, agreement, or similar item.
-
D.
mayActThrough
Indicates that an entity can exert influence, perform an action, or have an effect by means of another entity, mechanism, or intermediary.
-
E.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
- F. None of above. chosen
Provenance (4 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d98c3ab08190a1830c45578056ac |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:25 p.m.