Triple
T7486189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 393 U.S. 503 |
E176887
|
entity |
| Predicate | parallelCitation |
P18528
|
FINISHED |
| Object | 89 S. Ct. 733 |
—
|
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: 89 S. Ct. 733 | Statement: [393 U.S. 503, parallelCitation, 89 S. Ct. 733]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelCitation Context triple: [393 U.S. 503, parallelCitation, 89 S. Ct. 733]
-
A.
parallelPassage
Indicates that one text segment corresponds closely in content or structure to another, such that they can be considered parallel versions or accounts of the same material.
-
B.
citations
Indicates that one entity references another as a source of information, evidence, or authority, typically in a scholarly or informational context.
-
C.
subsequentCitationIn
Indicates that one work cites or references another work that appears later in a specified source or sequence.
-
D.
laterCitationForm
chosen
Indicates that one citation form is a subsequent or later version of another citation form for the same referenced work.
-
E.
subsequentCitationBy
Indicates that one work is cited by another work that was produced or published at a later time.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f556955c8190bf014a065e04c5d8 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.