Triple
T6745682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medgar Evers College |
E154205
|
entity |
| Predicate | namedForCause |
P10437
|
FINISHED |
| Object | American civil rights movement |
—
|
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: American civil rights movement | Statement: [Medgar Evers College, namedForCause, American civil rights movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForCause Context triple: [Medgar Evers College, namedForCause, American civil rights movement]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
C.
causeSupported
chosen
Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
-
D.
namedForConflict
Indicates that one entity is named after, or in commemoration of, a specific conflict, war, or battle.
-
E.
namedIn
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
- 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_69c6880ef37881909268a5a7299b9293 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1b74ae081908575c4e47c0ef297 |
completed | March 27, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:10 p.m.