Triple
T10673693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taney Court |
E251558
|
entity |
| Predicate | hasIdeologicalTendency |
P31611
|
FINISHED |
| Object | states’ rights |
—
|
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: states’ rights | Statement: [Taney Court, hasIdeologicalTendency, states’ rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdeologicalTendency Context triple: [Taney Court, hasIdeologicalTendency, states’ rights]
-
A.
hasIdeologicalPosition
chosen
Indicates that an entity holds, endorses, or is associated with a particular ideological stance or viewpoint.
-
B.
hasIdeologicalOrigin
Indicates that something originates from, is derived from, or is fundamentally based on a particular ideology.
-
C.
politicalTendency
Indicates the general political orientation, leaning, or ideological stance associated with an entity in relation to the political spectrum.
-
D.
hasIdeologicalRole
Indicates that an entity holds or fulfills a specific function, position, or influence within an ideology or ideological framework.
-
E.
ideologicalInfluence
Indicates that one entity’s beliefs, values, or doctrines shape, guide, or significantly affect the ideology of another entity.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fb9299708190a0a3818f2e4e9bf5 |
completed | April 9, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:09 p.m.