Triple
T383735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atomic Energy Act of 1954 |
E8734
|
entity |
| Predicate | primaryCitation |
P771
|
FINISHED |
| Object | 42 U.S.C. § 2011 et seq. |
—
|
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: 42 U.S.C. § 2011 et seq. | Statement: [Atomic Energy Act of 1954, primaryCitation, 42 U.S.C. § 2011 et seq.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCitation Context triple: [Atomic Energy Act of 1954, primaryCitation, 42 U.S.C. § 2011 et seq.]
-
A.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
B.
notablePrimary
Indicates that one entity is the main or most prominent example, instance, or representative of another entity.
-
C.
citation
chosen
Indicates that one entity references, quotes, or otherwise acknowledges another entity as a source of information or authority.
-
D.
primaryCriterion
Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
-
E.
citationBy
Indicates that one work is cited or referenced by another work.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec422b808190b6ddf747ef939151 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96602188190b0cbc167f55a9237 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.