Triple
T111580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Endangered Species Act |
E2258
|
entity |
| Predicate | uscSections |
P3120
|
FINISHED |
| Object | 16 U.S.C. §1531–1544 |
—
|
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: 16 U.S.C. §1531–1544 | Statement: [U.S. Endangered Species Act, uscSections, 16 U.S.C. §1531–1544]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uscSections Context triple: [U.S. Endangered Species Act, uscSections, 16 U.S.C. §1531–1544]
-
A.
section
chosen
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
B.
section7Provides
Indicates that Section 7 serves as the source or provider of something (such as rights, obligations, benefits, or content) to another party or element.
-
C.
subtitle
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
-
D.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
E.
textOfSection1
Indicates that the referenced text is the content belonging specifically to section 1 of a larger document or structure.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258b58efc8190959c86f73d67b744 |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25641058c8190b5b64509b35d8176 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.