Triple
T485172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irina Karamanos |
E9858
|
entity |
| Predicate | policyInterest |
P1876
|
FINISHED |
| Object | institutional design |
—
|
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: institutional design | Statement: [Irina Karamanos, policyInterest, institutional design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyInterest Context triple: [Irina Karamanos, policyInterest, institutional design]
-
A.
policyFocus
chosen
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.
-
B.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
-
C.
policyLevel
Indicates the degree or tier of strictness, scope, or priority associated with a given policy.
-
D.
representsInterestOf
Indicates that one entity expresses, holds, or embodies an interest, concern, or stake in another entity or subject.
-
E.
politicalGoal
Indicates a relationship where an entity aims to achieve, promote, or realize a specific political outcome, policy, or state of affairs.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0bb46788190b40182bf2a54f98f |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf48ec08190b85d07e194f99c49 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.