Triple
T7460703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia Register |
E176239
|
entity |
| Predicate | typeOfLawSource |
P65906
|
FINISHED |
| Object | primary legal source |
—
|
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: primary legal source | Statement: [District of Columbia Register, typeOfLawSource, primary legal source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLawSource Context triple: [District of Columbia Register, typeOfLawSource, primary legal source]
-
A.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
B.
majorLegalSource
chosen
Indicates that one entity serves as a primary or authoritative legal basis or reference for another entity.
-
C.
typeOfLawCollection
Indicates that a given collection is categorized as a specific type of law collection (e.g., by legal domain, jurisdiction, or purpose).
-
D.
legalCodeFocus
Indicates that something is specifically concerned with, centered on, or primarily addressing a particular legal code or body of law.
-
E.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d525708190b7838e07ac2fbe1f |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:38 p.m.