Triple
T25301171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | assassination attempts on Charles de Gaulle |
E634345
|
entity |
| Predicate | hasSecurityAgencyResponse |
P173190
|
FINISHED |
| Object | French police |
—
|
NE NERFINISHED |
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: French police | Statement: [assassination attempts on Charles de Gaulle, hasSecurityAgencyResponse, French police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityAgencyResponse Context triple: [assassination attempts on Charles de Gaulle, hasSecurityAgencyResponse, French police]
-
A.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
B.
hasSecurityBody
Indicates that an entity is protected or accompanied by a designated security body or security personnel.
-
C.
hasSecurityTeam
Indicates that an entity is supported or protected by a designated security team responsible for its safety or security operations.
-
D.
hasSecurityScreening
Indicates that an entity is subject to, or has undergone, a security screening process.
-
E.
hasSecurityRegime
Indicates that an entity is governed, protected, or controlled by a particular security regime, framework, or set of security rules.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 21, 2026, 1:24 p.m.