Triple
T25722141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hizb ut-Tahrir |
E645021
|
entity |
| Predicate | publiclyRejects |
P107359
|
FINISHED |
| Object | participation in armed struggle as an organization |
—
|
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: participation in armed struggle as an organization | Statement: [Hizb ut-Tahrir, publiclyRejects, participation in armed struggle as an organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyRejects Context triple: [Hizb ut-Tahrir, publiclyRejects, participation in armed struggle as an organization]
-
A.
disapprovedOf
chosen
Indicates that one entity holds a negative judgment or lack of approval toward another entity or that entity’s actions.
-
B.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
C.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
D.
canRejectWith
Indicates that one entity has the authority or ability to refuse, decline, or dismiss another entity or proposal using a specific method or condition.
-
E.
positionRejected
Indicates that an offered position, role, or job has been declined or not accepted by the relevant party.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 21, 2026, 10:02 p.m.