Triple
T8262416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Al |
E193224
|
entity |
| Predicate | safetyAndSecurityPolicy |
P8728
|
FINISHED |
| Object | armed in‑flight security personnel |
—
|
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: armed in‑flight security personnel | Statement: [El Al, safetyAndSecurityPolicy, armed in‑flight security personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyAndSecurityPolicy Context triple: [El Al, safetyAndSecurityPolicy, armed in‑flight security personnel]
-
A.
safetySetting
Indicates that an entity is configured with a particular safety-related parameter, mode, or constraint governing how it operates or behaves.
-
B.
explainsPolicy
Indicates that one entity provides a clarification or detailed description of a policy to another entity.
-
C.
securityArrangementsBy
chosen
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
D.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
E.
safetyProfile
Indicates the overall level and characteristics of risk or harm associated with something, typically summarizing how safe it is under specified conditions.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7938723081909379cf78a4449b80 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.