Triple
T48580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helvering v. Davis |
E954
|
entity |
| Predicate | pageInUnitedStatesReports |
P1468
|
FINISHED |
| Object | 619 |
—
|
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: 619 | Statement: [Helvering v. Davis, pageInUnitedStatesReports, 619]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pageInUnitedStatesReports Context triple: [Helvering v. Davis, pageInUnitedStatesReports, 619]
-
A.
officiallyReports
Indicates that one entity formally provides information, updates, or accountability to another entity within an official or authorized reporting structure.
-
B.
intelligenceUnitUnitedStates
Indicates a relationship where an intelligence unit is part of, operated by, or otherwise affiliated with the United States.
-
C.
pages
chosen
Indicates that one entity consists of or contains a certain number of pages, or that a specific page-related attribute is associated with it.
-
D.
statutesAtLargeCitation
Indicates that one entity cites or is referenced by a specific citation in the United States Statutes at Large.
-
E.
gdpRankInUS
Indicates the relative position of an entity in the ranking of U.S. entities based on their Gross Domestic Product (GDP).
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abe7cb481908d969e54032f6c75 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.