Triple
T21084897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tax Court |
E519460
|
entity |
| Predicate | proceduresInclude |
P67337
|
FINISHED |
| Object | filing of petitions by taxpayers |
—
|
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: filing of petitions by taxpayers | Statement: [Tax Court, proceduresInclude, filing of petitions by taxpayers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduresInclude Context triple: [Tax Court, proceduresInclude, filing of petitions by taxpayers]
-
A.
proceduresDefinedBy
Indicates that certain procedures are specified, established, or authored by a particular entity.
-
B.
proceduresVaryBy
Indicates that the procedures or methods used differ depending on a specified factor, context, or category.
-
C.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
-
D.
typeOfProcedureHandled
chosen
Indicates the specific kind or category of procedure that an entity is responsible for managing or processing.
-
E.
includesRoutine
Indicates that one entity contains or encompasses another entity as a regular or standard part of its routine or procedure.
- 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.