Triple
T15126335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southampton County, Virginia |
E361298
|
entity |
| Predicate | hasNotableHistoricEvent |
P2107
|
FINISHED |
| Object | 1831 slave rebellion led by Nat Turner |
—
|
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: 1831 slave rebellion led by Nat Turner | Statement: [Southampton County, Virginia, hasNotableHistoricEvent, 1831 slave rebellion led by Nat Turner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableHistoricEvent Context triple: [Southampton County, Virginia, hasNotableHistoricEvent, 1831 slave rebellion led by Nat Turner]
-
A.
hasHistoricalEvent
chosen
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
hasNamesakeNotableEvent
Indicates that one entity serves as the namesake for a notable event associated with the other entity.
-
C.
hasHistoricEventYear
Indicates the specific year in which a referenced historic event took place.
-
D.
hasNotablePersonEvent
Indicates that there exists a significant event in which the person plays a notable or central role.
-
E.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005a1b9288190954f2d92549805e5 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.