Triple
T15294596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beit Hanun |
E365619
|
entity |
| Predicate | frequentlySubjectTo |
P1313
|
FINISHED |
| Object | military operations |
—
|
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: military operations | Statement: [Beit Hanun, frequentlySubjectTo, military operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentlySubjectTo Context triple: [Beit Hanun, frequentlySubjectTo, military operations]
-
A.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
B.
isFrequentlyPerformedBy
Indicates that an action or activity is carried out often or on a regular basis by a particular entity.
-
C.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
D.
frequentOccasion
Indicates that a particular event, situation, or condition occurs repeatedly or commonly over time.
-
E.
isOftenRequiredFor
Indicates that one entity is frequently needed or commonly necessary for the occurrence, use, or success of another entity or activity.
- 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.