Triple
T18092346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of New Jersey v. Rubin Carter |
E433001
|
entity |
| Predicate | federalDecisionYear |
P2233
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [State of New Jersey v. Rubin Carter, federalDecisionYear, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: federalDecisionYear Context triple: [State of New Jersey v. Rubin Carter, federalDecisionYear, 1985]
-
A.
yearDecided
chosen
Indicates the specific calendar year in which a decision, ruling, or resolution was formally made or finalized.
-
B.
congressionalApprovalYear
Indicates the year in which a given item, action, or measure received formal approval by a legislative congress.
-
C.
firstClearlyRecognizedInDecisionYear
Indicates the year in which something was first clearly and explicitly recognized in a formal decision.
-
D.
federalPartCameIntoForce
Indicates that a specific part of a federal law or regulation has officially taken legal effect from a certain point in time.
-
E.
amendmentYear
Indicates the year in which an amendment to a law, document, or agreement was formally made or enacted.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd1972a881908072990de0715547 |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.