Triple
T18793559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Likud |
E459576
|
entity |
| Predicate | politicalPositionOnSecurity |
P89137
|
FINISHED |
| Object | hawkish |
—
|
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: hawkish | Statement: [Likud, politicalPositionOnSecurity, hawkish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalPositionOnSecurity Context triple: [Likud, politicalPositionOnSecurity, hawkish]
-
A.
positionOnSecurity
chosen
Indicates the stance, opinion, or policy an entity holds regarding security-related issues or measures.
-
B.
politicalPositionOnElectoralPolitics
Indicates a stance or viewpoint an entity holds regarding participation in, support for, or opposition to electoral political processes and institutions.
-
C.
politicalPositionAssociated
Indicates that there is an association between an entity and a specific political position, role, or office.
-
D.
positionOnSecurityTreaty
Indicates the stance or viewpoint an entity holds regarding a specific security treaty.
-
E.
politicalAttitude
Indicates an individual's stance, opinion, or orientation toward political issues, ideologies, or actors.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a01cc0c0819098ef4326e82ff524 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.