Triple
T15294577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | بيت حانون |
E365618
|
entity |
| Predicate | hasSecurityCondition |
P46890
|
FINISHED |
| Object | منطقة توتر أمني دائم |
—
|
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: منطقة توتر أمني دائم | Statement: [بيت حانون, hasSecurityCondition, منطقة توتر أمني دائم]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityCondition Context triple: [بيت حانون, hasSecurityCondition, منطقة توتر أمني دائم]
-
A.
hasSecurityClause
Indicates that an agreement, contract, or document includes a provision specifying security-related requirements, protections, or safeguards.
-
B.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
C.
hasSecurityFunction
Indicates that an entity performs, provides, or is responsible for a security-related role, protection mechanism, or safeguarding function for another entity or system.
-
D.
hasSecurityDimension
chosen
Indicates that something possesses or is associated with a particular aspect or dimension of security.
-
E.
hasSecurityAccessControl
Indicates that an entity enforces or is associated with mechanisms that regulate and control access to resources or information for security purposes.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03682ea488190ac82fdbd0e855d34 |
completed | April 16, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.