Triple
T6265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Democratic Party |
E125
|
entity |
| Predicate | opposesPolicy |
P437
|
FINISHED |
| Object | large-scale deregulation of business |
—
|
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: large-scale deregulation of business | Statement: [Democratic Party, opposesPolicy, large-scale deregulation of business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposesPolicy Context triple: [Democratic Party, opposesPolicy, large-scale deregulation of business]
-
A.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
C.
advocates
Indicates that one entity publicly supports, recommends, or argues in favor of another entity or its interests.
-
D.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
E.
elects
Indicates that one entity selects or chooses another entity for a position, role, or office, typically through a formal voting process.
- 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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a2421836f08190b54fc40edeb1a96b |
completed | Feb. 28, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69a23fe064c881909496fd0e6b0e18d7 |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.