Triple
T20358598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edelman v. Jordan |
E496715
|
entity |
| Predicate | limitedScopeOf |
P30064
|
FINISHED |
| Object | federal court relief against state officials |
—
|
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: federal court relief against state officials | Statement: [Edelman v. Jordan, limitedScopeOf, federal court relief against state officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedScopeOf Context triple: [Edelman v. Jordan, limitedScopeOf, federal court relief against state officials]
-
A.
limitedPracticeOf
Indicates that one entity engages in or allows only a restricted or reduced extent of a particular practice, activity, or method in relation to another entity.
-
B.
reductionOfScope
chosen
Indicates a relationship where the extent, coverage, or range of something is decreased or limited compared to its previous or potential scope.
-
C.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
D.
limitedIssueOf
Indicates that one entity is issued or made available in a restricted or finite quantity by another entity.
-
E.
limitsDefinitionTo
Indicates that one entity constrains or narrows the scope of how another entity is defined or interpreted.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67855c3a88190b88839a47d01184d |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.