Triple
T27802470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Still |
E702283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conductor on the Underground Railroad |
C26143
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: conductor on the Underground Railroad Context triple: [William Still, instanceOf, conductor on the Underground Railroad]
-
A.
Underground Railroad operative
chosen
An Underground Railroad operative is a clandestine individual who secretly aids enslaved people in escaping bondage by providing guidance, shelter, resources, and coordination along covert routes to freedom.
-
B.
Underground Railroad document
An Underground Railroad document is a historical record—such as letters, maps, narratives, or legal papers—that provides evidence of the people, routes, operations, and experiences associated with the clandestine network that aided enslaved individuals in escaping to freedom.
-
C.
rescue of a fugitive slave
The "rescue of a fugitive slave" class represents actions and events in which individuals or groups intervene to free an escaped enslaved person from capture, detention, or return to enslavement.
-
D.
slave rebellion leader
A slave rebellion leader is an enslaved person who organizes, inspires, and directs collective resistance against enslavement, often at great personal risk, to challenge and overthrow oppressive systems.
-
E.
Confederate agent
A Confederate agent is an individual who covertly gathered intelligence, conducted sabotage, or engaged in clandestine operations in support of the Confederate States during the American Civil War.
- F. None of above.
Provenance (1 batch)
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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:35 p.m.