Triple
T11664610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Tax Court Building |
E277214
|
entity |
| Predicate | jurisdictionOfCourtHoused |
P74432
|
FINISHED |
| Object | federal tax disputes |
—
|
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: federal tax disputes | Statement: [U.S. Tax Court Building, jurisdictionOfCourtHoused, federal tax disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jurisdictionOfCourtHoused Context triple: [U.S. Tax Court Building, jurisdictionOfCourtHoused, federal tax disputes]
-
A.
jurisdictionOfPrimaryCourt
Indicates the geographic or legal scope within which a primary court has the authority to hear and decide cases.
-
B.
courtLocation
Indicates the place or venue where a court proceeding or judicial action takes place.
-
C.
courtBasedIn
Indicates that a particular court is located or headquartered in a specified place or jurisdiction.
-
D.
courthouseLocatedIn
Indicates that a courthouse is situated within or at a specific geographic or administrative location.
-
E.
jurisdictionOfTribunal
chosen
Indicates the legal authority or scope within which a particular tribunal is empowered to hear and decide cases.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d3a64c819099f398ea22c8c180 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.