Triple
T23635154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Posse Comitatus Act |
E583722
|
entity |
| Predicate | codifiedInSection |
P775
|
FINISHED |
| Object | 18 U.S.C. § 1385 |
—
|
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: 18 U.S.C. § 1385 | Statement: [Posse Comitatus Act, codifiedInSection, 18 U.S.C. § 1385]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codifiedInSection Context triple: [Posse Comitatus Act, codifiedInSection, 18 U.S.C. § 1385]
-
A.
codifiedIn
chosen
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
B.
codifiedUnderAuthority
Indicates that something has been formally established, defined, or recorded according to the rules or power of a specific authority.
-
C.
governsSectionOf
Indicates that one entity has authoritative control or regulatory oversight over a specific section or part of another entity.
-
D.
chapterOfLaw
Indicates that one legal text or section is a chapter belonging to a specific law or legal act.
-
E.
codeSection
Indicates a specific segment or subsection within a larger body of code that is distinguished for reference, organization, or analysis.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1eb38a481909f7ceeaefb7b43ce |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:47 p.m.