Triple
T29250909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reuben Scott |
E741563
|
entity |
| Predicate | setWithinHistoricalContext |
P1409
|
FINISHED |
| Object | post-slavery United States |
—
|
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: post-slavery United States | Statement: [Reuben Scott, setWithinHistoricalContext, post-slavery United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setWithinHistoricalContext Context triple: [Reuben Scott, setWithinHistoricalContext, post-slavery United States]
-
A.
hasHistoricalContext
chosen
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
B.
locatedInHistoricContext
Indicates that an entity is situated within or associated with a historically significant setting, period, or environment.
-
C.
hasHistoricalContextDisplays
Indicates that something presents or showcases information within a broader historical background or setting.
-
D.
shareHistoricalContextAs
Indicates that two or more entities are associated with or understood within the same historical background, period, or circumstances.
-
E.
historicallyEncompassed
Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical period.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6648ce9508190a250cf77d9181422 |
completed | May 2, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:34 p.m.