Triple
T21084912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tax Court |
E519460
|
entity |
| Predicate | decisionsMayBeAppealedTo |
P17875
|
FINISHED |
| Object | higher courts |
—
|
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: higher courts | Statement: [Tax Court, decisionsMayBeAppealedTo, higher courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionsMayBeAppealedTo Context triple: [Tax Court, decisionsMayBeAppealedTo, higher courts]
-
A.
canBeAppealedTo
chosen
Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
-
B.
decisionsCalled
Indicates that one entity has made or issued formal decisions that are referred to or invoked by another entity.
-
C.
decisionsAre
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
-
D.
decisionsCitableAs
Indicates that certain decisions can be formally cited as authoritative references or precedents in relevant contexts.
-
E.
decisionsTakenBy
Indicates that one or more decisions are made or taken by a specified agent or entity.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e709498fc081908d92a93e8678c140 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:49 p.m.