Triple
T28581053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Carolene Products Co. |
E723377
|
entity |
| Predicate | footnoteNumber |
P164652
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [United States v. Carolene Products Co., footnoteNumber, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footnoteNumber Context triple: [United States v. Carolene Products Co., footnoteNumber, 4]
-
A.
followsNumbering
Indicates that one entity adheres to or continues the numbering sequence established by another entity.
-
B.
numberingReason
Indicates the rationale or basis for assigning a particular number or numbering scheme to something.
-
C.
numberingStatus
Indicates the status or condition of an entity’s assigned number or numbering process (e.g., whether it has been numbered, is pending, or has a particular numbering state).
-
D.
frontNumbering
Indicates that an entity is assigned a numbering or label that appears at the front or beginning of something (e.g., a sequence, document, or list).
-
E.
numberingType
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650cbb3348190977e970d2986a846 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 4:15 a.m.