Triple
T16142962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Osawatomie |
E391707
|
entity |
| Predicate | strengthProSlavery |
P121276
|
FINISHED |
| Object | approximately 250–400 men |
—
|
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: approximately 250–400 men | Statement: [Battle of Osawatomie, strengthProSlavery, approximately 250–400 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthProSlavery Context triple: [Battle of Osawatomie, strengthProSlavery, approximately 250–400 men]
-
A.
positionOnSlavery
Indicates a stance, opinion, or policy that an entity holds regarding the institution or practice of slavery.
-
B.
effectOnSlavery
Indicates the impact or influence that something has on the existence, extent, or conditions of slavery.
-
C.
legalStatusOfSlavery
Indicates the legal condition or permissibility of slavery within a given jurisdiction, time, or context.
-
D.
wasFormerlyEnslaved
Indicates that an entity was previously held in a condition of slavery or bondage but is no longer enslaved.
-
E.
attitudeTowardSlaves
Indicates a person's stance, feelings, or views regarding the institution or practice of slavery and enslaved individuals.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9082588190bc7e6ff491f0d94e |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1835b64948190ae1d2a9d4cc64acf |
completed | April 17, 2026, 12:48 a.m. |
Created at: April 10, 2026, 5:01 a.m.