Triple
T7143848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WIN button |
E166514
|
entity |
| Predicate | relatedPolicyIssue |
P25878
|
FINISHED |
| Object | inflation |
—
|
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: inflation | Statement: [WIN button, relatedPolicyIssue, inflation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedPolicyIssue Context triple: [WIN button, relatedPolicyIssue, inflation]
-
A.
commonPolicyArea
Indicates that two entities share the same policy domain, topic, or area of regulatory or legislative focus.
-
B.
politicalIssueIn
Indicates that a political issue is relevant to, occurs within, or is associated with a particular geographic or political region.
-
C.
politicalIssueFor
chosen
Indicates a relationship where a particular topic, problem, or policy area is considered a matter of political concern or debate for a given entity.
-
D.
policyFocus
Indicates that an entity (such as a person, organization, or document) is primarily concerned with, directed toward, or centered on a particular policy area or issue.
-
E.
relatedLegislation
Indicates that there exists a legislative document that is connected to, affects, or is otherwise relevant to the subject 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7d027d0819088598b2a9f71b1b7 |
completed | March 27, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.