Triple
T26573247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota ex rel. Floyd B. Olson |
E666881
|
entity |
| Predicate | courtOfOrigin |
P8824
|
FINISHED |
| Object | Minnesota state court |
—
|
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: Minnesota state court | Statement: [Minnesota ex rel. Floyd B. Olson, courtOfOrigin, Minnesota state court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtOfOrigin Context triple: [Minnesota ex rel. Floyd B. Olson, courtOfOrigin, Minnesota state court]
-
A.
originatingJurisdiction
Indicates the jurisdiction (such as a country, state, or legal authority) from which something originally comes or under whose laws it was first established.
-
B.
originatedInCourtOf
Indicates that a legal case, decision, or proceeding began or was first filed in a specified court.
-
C.
originatingStateCourt
chosen
Indicates the court in which a legal case or proceeding was originally filed or initiated.
-
D.
courtName
Indicates the official name assigned to a particular court within a legal or judicial system.
-
E.
courtBasedIn
Indicates that a particular court is located or headquartered in a specified place or jurisdiction.
- 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_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 1:59 a.m.