Triple
T28813880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lecompton |
E727586
|
entity |
| Predicate | politicalAlignmentIn1850s |
P143161
|
FINISHED |
| Object | pro-slavery |
—
|
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: pro-slavery | Statement: [Lecompton, politicalAlignmentIn1850s, pro-slavery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalAlignmentIn1850s Context triple: [Lecompton, politicalAlignmentIn1850s, pro-slavery]
-
A.
politicalAlignmentIn19thCentury
chosen
Indicates the political stance or ideological orientation an entity held during the 19th century.
-
B.
countryIn19thCentury
Indicates that an entity functioned as a country at some point during the 19th century.
-
C.
UnionPolicy1864
Indicates a formal policy, decision, or set of rules established by a union in the year 1864 that governs or defines how the union acts or relates to other parties.
-
D.
traditionalPoliticalAlignment
Indicates how closely an entity’s political views or affiliations align with established, historically dominant, or customary political positions within a given context.
-
E.
economicAlignment
Indicates that two or more entities share similar or compatible economic interests, policies, or strategic economic objectives.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 28, 2026, 6:32 a.m.