Triple
T28816227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solid South |
E727645
|
entity |
| Predicate | notableBreak |
P203498
|
FINISHED |
| Object | 1948 presidential election |
—
|
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: 1948 presidential election | Statement: [Solid South, notableBreak, 1948 presidential election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBreak Context triple: [Solid South, notableBreak, 1948 presidential election]
-
A.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
B.
notableBlock
Indicates that one entity is a block (e.g., text, code, or content segment) that is considered notable or significant in relation to another entity or context.
-
C.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
-
D.
notableBroadcast
Indicates that an entity is recognized for having made a significant or widely known broadcast.
-
E.
notableDeparture
Indicates that an entity has left a position, place, or role in a way that is significant or noteworthy.
- F. None of above. chosen
Provenance (4 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a0191d96dc88190ac0823e534f9d704 |
completed | May 11, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_6a01908110448190a46442ffe4d15f5f |
completed | May 11, 2026, 8:17 a.m. |
| PDg | Predicate description generation | batch_6a0191d8cc888190859143c9e459653a |
completed | May 11, 2026, 8:22 a.m. |
Created at: April 28, 2026, 6:32 a.m.