Triple
T22345904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service de Renseignement Zéro |
E552389
|
entity |
| Predicate | riskToMembers |
P147863
|
FINISHED |
| Object | arrest |
—
|
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: arrest | Statement: [Service de Renseignement Zéro, riskToMembers, arrest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskToMembers Context triple: [Service de Renseignement Zéro, riskToMembers, arrest]
-
A.
riskToUser
Indicates that something poses a potential danger, harm, or adverse impact to the user.
-
B.
riskListedBy
Indicates that a risk has been documented, identified, or cataloged by a particular agent or source.
-
C.
riskTakenFor
Indicates that one entity accepts or undertakes a risk for the benefit, protection, or sake of another entity.
-
D.
riskToSpeaker
Indicates that the action, event, or situation poses a potential danger, harm, or adverse consequence to the speaker.
-
E.
riskTaken
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
- F. None of above. chosen
Provenance (4 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157981c0881909ac74d68b99075c2 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:43 p.m.