Triple
T23703463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appeals Arbitration Division |
E585654
|
entity |
| Predicate | maySetAside |
P49338
|
FINISHED |
| Object | decision under appeal |
—
|
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: decision under appeal | Statement: [Appeals Arbitration Division, maySetAside, decision under appeal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySetAside Context triple: [Appeals Arbitration Division, maySetAside, decision under appeal]
-
A.
canSetAside
chosen
Indicates that one entity has the authority or ability to annul, override, or render ineffective a decision, rule, or arrangement associated with another entity.
-
B.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
C.
mayRemove
Indicates that one entity is permitted or authorized to remove another entity or its association.
-
D.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
E.
maySuspend
Indicates that one entity has the authority or permission to temporarily suspend another entity or its associated activity, status, or operation.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b684e0a88190b7edeb102585ae9d |
completed | April 29, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.