Triple
T32906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Reports |
E656
|
entity |
| Predicate | isCitedIn |
P771
|
FINISHED |
| Object | legal briefs |
—
|
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: legal briefs | Statement: [United States Reports, isCitedIn, legal briefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCitedIn Context triple: [United States Reports, isCitedIn, legal briefs]
-
A.
citation
chosen
Indicates that one entity references, quotes, or otherwise acknowledges another entity as a source of information or authority.
-
B.
peerReviewed
Indicates that a work, study, or submission has been evaluated and critiqued by qualified experts in the same field before acceptance or publication.
-
C.
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.
-
D.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
E.
peerReview
Indicates that one entity evaluates, critiques, or validates the work or performance of another entity, typically as an equal in expertise or status.
- 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_69a2496ffc548190b545f998cbebd5b9 |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a248717f5081909952a8c9ed1e1742 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.