Triple
T11054698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas v. White |
E261344
|
entity |
| Predicate | hasVolumeInUnitedStatesReports |
P3130
|
FINISHED |
| Object | 74 |
—
|
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: 74 | Statement: [Texas v. White, hasVolumeInUnitedStatesReports, 74]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolumeInUnitedStatesReports Context triple: [Texas v. White, hasVolumeInUnitedStatesReports, 74]
-
A.
volumeInUnitedStatesReports
chosen
Indicates that a legal case or decision is published in a specified volume of the United States Reports.
-
B.
hasUSAN
Indicates that an entity has a specified United States Adopted Name (USAN), typically a nonproprietary name assigned to a pharmaceutical substance.
-
C.
requiresFromUnitedStates
Indicates that one entity has a requirement that must be fulfilled specifically by the United States.
-
D.
purchasedByUnitedStatesIn
Indicates that something was bought or acquired by the United States during a specified time period.
-
E.
isInUnitedStates
Indicates that one entity is located within the geographic or political boundaries of the United States.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a0890481909c1d4f9d5b23f33a |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.