Triple
T4268371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heman Marion Sweatt |
E96879
|
entity |
| Predicate | causeChampioned |
P27369
|
FINISHED |
| Object | desegregation of higher education |
—
|
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 higher education | Statement: [Heman Marion Sweatt, causeChampioned, desegregation of higher education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeChampioned Context triple: [Heman Marion Sweatt, causeChampioned, desegregation of higher education]
-
A.
causeSupported
Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
-
B.
debatedAsCauseOf
Indicates that one entity is discussed or argued over as a possible cause or origin of another entity.
-
C.
championedBy
chosen
Indicates that an entity is actively supported, promoted, or advocated for by another entity.
-
D.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ff913608190b6ccf4a85057b07b |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.