Triple
T26573246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota ex rel. Floyd B. Olson |
E666881
|
entity |
| Predicate | caseNameContext |
P141395
|
FINISHED |
| Object | Near v. Minnesota |
—
|
NE NERFINISHED |
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: Near v. Minnesota | Statement: [Minnesota ex rel. Floyd B. Olson, caseNameContext, Near v. Minnesota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseNameContext Context triple: [Minnesota ex rel. Floyd B. Olson, caseNameContext, Near v. Minnesota]
-
A.
caseNameVariant
chosen
Indicates that one case name is an alternative or variant form of another case name.
-
B.
caseNameDerivedFrom
Indicates that the name of a legal case is derived from, or based on, another specified source or entity.
-
C.
notableCaseContext
Indicates that an entity is associated with a particular contextual detail, circumstance, or background information relevant to a notable case or instance.
-
D.
contextName
Indicates the specific contextual label or identifier under which an entity, event, or relation is defined or interpreted.
-
E.
caseNumber
Indicates the unique identifying number assigned to a particular legal or administrative case.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614a659748190a89f7b86055fa624 |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:59 a.m.