Triple
T9420753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumner, Mississippi |
E227142
|
entity |
| Predicate | historicalEraOfNotability |
P561
|
FINISHED |
| Object | Civil Rights Movement era |
—
|
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: Civil Rights Movement era | Statement: [Sumner, Mississippi, historicalEraOfNotability, Civil Rights Movement era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEraOfNotability Context triple: [Sumner, Mississippi, historicalEraOfNotability, Civil Rights Movement era]
-
A.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
B.
historicalNotability
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
C.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its name.
-
D.
notableEraNickname
Indicates the informal or popular nickname by which a particular historical era or period is commonly known.
-
E.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c2528c8819087b0a21e703254b7 |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.