Triple
T3149281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Tax Court |
E65836
|
entity |
| Predicate | establishedAsArticleICourt |
P46393
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [United States Tax Court, establishedAsArticleICourt, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsArticleICourt Context triple: [United States Tax Court, establishedAsArticleICourt, 1969]
-
A.
servedAtCourtOf
Indicates that an individual performed official duties or held a position in the court of a particular ruler or governing authority.
-
B.
judicialArticle
Indicates that there is a specific legal or judicial article that governs, defines, or is applied to the relationship or action between the entities.
-
C.
originatedInCourt
Indicates that a legal case, decision, or proceeding began or was first filed in a specified court.
-
D.
createdCourt
Indicates that an entity (typically a person or organization) established or founded a particular court.
-
E.
nominatedToCourtOn
Indicates that an entity has been formally proposed or selected for appointment to a specific court on a particular date or occasion.
- F. None of above. chosen
Provenance (4 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5be30fc819097edb620c65055d5 |
completed | March 8, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:05 p.m.