Triple
T16963033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Board of Law Examiners |
E411475
|
entity |
| Predicate | mayDeny |
P42632
|
FINISHED |
| Object | admission to the Indiana bar |
—
|
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: admission to the Indiana bar | Statement: [Indiana Board of Law Examiners, mayDeny, admission to the Indiana bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayDeny Context triple: [Indiana Board of Law Examiners, mayDeny, admission to the Indiana bar]
-
A.
mayReject
chosen
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
B.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
C.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
-
D.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
-
E.
mayAdmit
Indicates that one entity has the permission or authority to allow another entity to enter, join, or be accepted into something.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0a1f6308190af5ad171630dacbf |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.