Triple
T7486066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronald H. Bradley et al. |
E176884
|
entity |
| Predicate | soughtRemedy |
P2242
|
FINISHED |
| Object | desegregation of Detroit public schools |
—
|
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: desegregation of Detroit public schools | Statement: [Ronald H. Bradley et al., soughtRemedy, desegregation of Detroit public schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtRemedy Context triple: [Ronald H. Bradley et al., soughtRemedy, desegregation of Detroit public schools]
-
A.
remedySought
chosen
Indicates that a particular legal or corrective action is being requested as a solution or relief in response to a problem or dispute.
-
B.
remedy
Indicates that one entity serves to cure, alleviate, or counteract a problem, illness, or undesirable condition affecting another entity.
-
C.
typeOfRemedy
Indicates that one entity is a specific kind or category of remedy in relation to another entity.
-
D.
soughtTo
Indicates that one entity attempted or intended to obtain, achieve, or bring about another entity or outcome.
-
E.
soughtAssistanceFrom
Indicates that one entity actively requested help, support, or guidance from another entity.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f556955c8190bf014a065e04c5d8 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.