Triple
T31360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Statutes at Large |
E625
|
entity |
| Predicate | citationUsedBy |
P771
|
FINISHED |
| Object | lawyers |
—
|
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: lawyers | Statement: [United States Statutes at Large, citationUsedBy, lawyers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citationUsedBy Context triple: [United States Statutes at Large, citationUsedBy, lawyers]
-
A.
citation
chosen
Indicates that one entity references, quotes, or otherwise acknowledges another entity as a source of information or authority.
-
B.
mentions
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
C.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a249ec0d288190ac3a0939db61813b |
completed | Feb. 28, 2026, 1:50 a.m. |
| PD | Predicate disambiguation | batch_69a24870417081909c7c01e400c94716 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.