Triple
T33711089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tariff of 1833 |
E863740
|
entity |
| Predicate | compromiseEngineeredBy |
P177227
|
FINISHED |
| Object | Henry Clay |
—
|
NE NERFINISHED |
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: Henry Clay | Statement: [Tariff of 1833, compromiseEngineeredBy, Henry Clay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compromiseEngineeredBy Context triple: [Tariff of 1833, compromiseEngineeredBy, Henry Clay]
-
A.
compromiseBetween
Indicates a relationship in which two or more parties mutually adjust their positions or demands to reach a middle-ground agreement.
-
B.
designCompromiseFor
Indicates a relationship where a design is adjusted or balanced to reach a compromise that addresses the needs, constraints, or preferences of a particular entity or situation.
-
C.
compromiseFeature
Indicates that one entity weakens, reduces, or negatively affects the quality, effectiveness, or integrity of a feature of another entity.
-
D.
engineeredBy
Indicates that an entity has been designed, created, or developed through the technical work or expertise of another entity.
-
E.
compromisePlan
Indicates that an entity develops, proposes, or adopts a plan intended to reconcile conflicting positions or interests between parties.
- 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae2a7a8819099945d1706a94bfd |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:43 a.m.