Triple
T12812984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Reply to Hayne |
E306316
|
entity |
| Predicate | legislativeIssue |
P8905
|
FINISHED |
| Object | tariff policy |
—
|
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: tariff policy | Statement: [Second Reply to Hayne, legislativeIssue, tariff policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeIssue Context triple: [Second Reply to Hayne, legislativeIssue, tariff policy]
-
A.
hasLegislativeSubject
chosen
Indicates that a legislative document, action, or body concerns, addresses, or is about a particular subject or topic.
-
B.
legislativeActOf
Indicates a relationship where a legislative act is authored, enacted, or formally issued by a specific legislative body or authority.
-
C.
politicalIssueIn
Indicates that a political issue is relevant to, occurs within, or is associated with a particular geographic or political region.
-
D.
legislativeActivity
Indicates involvement in creating, debating, amending, or passing laws or related legislative measures.
-
E.
legislativeImpact
Indicates the effect that a law or legislative action has on a policy, entity, or outcome.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9adcf08190a12801adcc613477 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.