Triple
T7476116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cox v. Louisiana |
E176636
|
entity |
| Predicate | hasParallelCitation |
P76460
|
FINISHED |
| Object | 85 S. Ct. 453 |
—
|
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: 85 S. Ct. 453 | Statement: [Cox v. Louisiana, hasParallelCitation, 85 S. Ct. 453]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParallelCitation Context triple: [Cox v. Louisiana, hasParallelCitation, 85 S. Ct. 453]
-
A.
hasCitationForm
Indicates that an entity is associated with a specific standardized form used for citing or referencing it.
-
B.
hasFullCitation
Indicates that an entity is associated with a complete and properly formatted bibliographic reference.
-
C.
hasSisterPublication
Indicates that one publication is related to another as a sister publication, typically under the same parent organization or closely associated in scope or branding.
-
D.
hasCitationSystem
Indicates that one entity uses, follows, or is governed by a particular citation or referencing system defined by another entity.
-
E.
isCitedFor
Indicates that one entity references another as a source of information, evidence, or authority for a specific claim, idea, or contribution.
- F. None of above. chosen
Provenance (4 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f4ec85488190a1f7fb913e0fbe35 |
completed | March 27, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f105e320819091db3cdb1f1351f0 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:41 p.m.