Triple
T35387619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Border ruffians |
E1022831
|
entity |
| Predicate | supportedLaw |
P31232
|
FINISHED |
| Object | Kansas–Nebraska Act |
E54193
|
NE 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: Kansas–Nebraska Act | Statement: [Border ruffians, supportedLaw, Kansas–Nebraska Act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedLaw Context triple: [Border ruffians, supportedLaw, Kansas–Nebraska Act]
-
A.
supportedLegislation
chosen
Indicates that an entity endorsed, promoted, or voted in favor of a particular piece of legislation.
-
B.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
C.
legalIn
Indicates that an action, status, or entity is permitted or valid under the laws or regulations of a specified jurisdiction.
-
D.
supportsJurisdiction
Indicates that one jurisdiction provides backing, authority, or legal support for the actions, decisions, or existence of another jurisdiction.
-
E.
containsLaw
Indicates that one entity (such as a document, code, or jurisdiction) includes or encompasses a specific law within it.
- F. None of above.
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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384022ee5081909dc89294eb8cfb17 |
completed | June 21, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.